Alert roll-up to parent components.

Question

Hi.

Does anyone know how the alerts are meant to roll-up from one component to another in the activity view, either via a depends on or contains relationship? In my tests some alerts seem to appear in the dependency list for the activity view of the parent component and other alerts do not appear at all. I've also seem some alerts appear twice for different components. I'm really not confident that this is working at all and am confused. Any pointers would be helpful.

Andy Davies · Answer

Hi @Enrique Serrano Valle - did you have any thoughts on this? Would love to get your feedback.

Andy Davies · Answer

Thanks for the reply @Enrique Serrano Valle . That's largely how I would expect it to work. However

1. Multiple Alerts

I posted a single API using Postman to a service I have defined called 'Shared Session Service' - this same alert then appears in sibling services. I don't believe this is expected behaviour.

The single api call made was:

{

"cloudId": "xxxxx",

"event": {

"alert": {

"displayName": "Shared Service",

"lastUpdated": "2025-10-01T14:14:00Z",

"updateSequenceNumber": 1,

"description": "Shared Service Alert #1",

"url": "http://www.google.co.uk",

"externalEventSourceId": "PagerDuty",

"alertProperties": {

"id": "Shared Service 1",

"status": "OPENED"

}

},

"componentId": "ari:cloud:compass:xxxxxxxx:component/xxxxxxx-45e3-a9e8-0b34a837100b/xxxxxxxx-4982-a824-5fde91d06a9f"

}

2. Roll-up depth

It would be good to be able to have alerts roll-up multiple levels rather than to just the parent in the relationship. This way if the alert occurs several levels deep a team can still see it on their activity diagrams showing them there might be a potential problem with their service. Going only one level deep potentially hides issues from the development team. I think there should be an option to enable this.

Enrique Serrano Valle · Answer

Hi, @Andy Davies !

When alerts are created, one or more Compass components can be assigned to the specified alert. These alerts would show up associated only to the specific Alerts row of that specific component.

When component A has a dependency on component B (e.g.: Depends On), navigating to the Activity Feed of component A would show events from other components under "dependencies" (but not the other way around). Alerts specifically assigned to component B would then be visible under Dependencies > Component B > Alerts

Here's an example of what that would look like: