Since a lot of service's these days are dependent on SNMP to monitor their status (Windows services/Linux Processes, etc). When SNMP goes down, so do all those services. This is basically the same theory as to why the Path Outages feature is used for. It would be nice to say that a service is dependent on SNMP and if SNMP is down, to suppress the alert. Also like how the node down event works, when it sees a service down it checks ICMP to see if the node is down in order to define the event type triggered (ie lost service or node down).
So on some of our nodes that have say 20 Windows services monitored and there is an SNMP outage we now get 21 alerts (20 + the SNMP alert).
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Christian Seifert March 12, 2013 at 12:53 PM
It would generally be nice to have the ability to define a "ParentService" for any service as the same thing happens when you use a lot of NRPE checks.
Since a lot of service's these days are dependent on SNMP to monitor their status (Windows services/Linux Processes, etc). When SNMP goes down, so do all those services. This is basically the same theory as to why the Path Outages feature is used for. It would be nice to say that a service is dependent on SNMP and if SNMP is down, to suppress the alert. Also like how the node down event works, when it sees a service down it checks ICMP to see if the node is down in order to define the event type triggered (ie lost service or node down).
So on some of our nodes that have say 20 Windows services monitored and there is an SNMP outage we now get 21 alerts (20 + the SNMP alert).