Enhancement: Monitor dependancies

[KoalaG]

Is your feature request related to a problem? Please describe. In complex networks, you will often have services that are reliant upon other services. For example, a virtual machine is reliant on the host machine operating, which is inturn reliant on a router for internet access. If the host machine was to stop working, then the virtual machines inside would also stop working, this could lead to over complication of incidents being created for the same reason.

Describe the solution you'd like A monitor should be able to select "parent" or "upstream" monitors which it is dependant on. In setting up the criteria of a monitor, if you are creating an incident, you should be able to choose to include child monitors as part of the incident. In turn, on a child monitor's criteria, you should be able to use the upstream monitors current status to determine if a criteria should be triggered.

Describe alternatives you've considered Not tested: Workflows could be used to a) turn off and on child monitors when a parent status is changed. This would be combersome to setup and manage compared to built-in functionality.

Additional context Having come from Site24x7, this was handled quite well, where notifications could be "supressed" on child monitors when a parent monitor was down.

[netstx]

This is an excellent suggestion.