Dependencies or Parent/Child Relationships

 

I'm happy to say this is on our road map.  I don't know much - in terms of how we'll configure it, the visuals, user experience, or timeline - but it will be one of the larger projects we focus on this year.  Keep the requests coming - especially any specifics in terms of which problems a feature like this may solve!

Hi Annie,

this is good news...

From my point of view: It would be nice to create dependencies between targets across servers of other objects like routers, switches etc.

Example: An application is running on server A where it's database is on server B. If we have a critical (or fatal) alert on the database, i would like to see that this will also impact the application object. Same thing when there is a critical alert on a server, this is most likely to impact anything that is running on this server.

Or, if I take it to a network level: If a router is going down, it will for sure impact all servers connected to this router (which will impact anything on these servers or depending on these)

In case this happens I would expect a target to get in a specified state (i.e. "related warning" or "related error"). Sending out alerts (for the childs) on this would not always be required as long as the original alert (i.e. networkswitch went down) is cleary indicating the impact based on the child relations. Or just an alert which refers to the original issue.

Kind regards,

Jeroen