Checkmk Services Dependencies across hosts
It would be great to have service dependencies across hosts for Checkmk, just like the host parent/child relationships.
In case that the parent service fails all the child services could go to stale and state that the parent service is down instead alerting all the depending Services.
In case of a downtime the parent service could inherit it's downtime on request to all the child services like it can be done with the host downtimes.
As an example:
If a web server is no longer running, the central active HTTP checks on the Checkmk server do not have to alarm.
I absolutely recommend this feature request
This would be very useful. For example, today, when a network interface service on host A goes CRIT, the VPN service on host B also goes CRIT, and we get 2 alerts for 1 issue. A dependency between the services would solve this.
It's possible to do that relationship using Business Intelligence Module.
The main task of the BI module is to aggregate the status of multiple services, not to distinguish between different causes.
To use Ian's example:
In case of a network fault, the network team must be alerted, and in case of a VPN fault, the VPN team must be alerted. But if the dependent network service is the cause, the VPN Service and all other dependent Services could become "Stale" and the VPN team must not be alerted.
Another advantage of dependencies:
If a downtime is defined for a parent service, it could optionally be applied to all child services as well, so that their service owners are not notified during this time. This is particularly useful in larger organizations with different responsibilities.
I support this feature request.
As a usage example: NFS-mounts need not be marked critical when the NFS-server providing the respective shares is down.
This would be useful for us, too.
We are monitoring a lot of switchports (e.g. for Performancedata)
Example: If a connected ESXi will be rebooted and is on downtime, we don't want an alert for the network team, because the host is in downtime
Fabrice Le Dorze
I'm coming from Nagios. This feature exists in Nagios 3 itself :
So I guess it's the case in CheckMk RAW in Nagios 3 engine. Am I right ?
It was there in the beginning but some people decided there is no need for it anymore ;-)
Maybe in the RAW idition, dont know - but guess most of the users here are not RAW Edition users, and there ist clearly missing
i would like that feature too, cause applications do use services from different servers, so if one of the servers providing those services goes down, no need to disturb the application guys by a notification, there is nothing they can do … but, they need to be informed about the planned downtime to inform their customers
I also support this.
We have primary api services and distributed mirrors that call the upstream service.
If the api service misbehaves, all the mirrors will show an error.
We would like to suppress alerts on the mirrors in case the primary is down.
But we do want the mirrors to be monitored because they themselves may misbehave.