This issue comes from an interesting discussion we have had privately an onto discussion list.
We do not have service hierarchy in Poller.
The only one is that established by what we called critical service.
We should address some use cases when try to use the really awesome SnmpMonitor to for example verify process running on similar facts:
The question is: what to do when the Agent is Down?
Clearly here we have a dependency from the availability of the Snmp agent on the remote host and if for example I'm monitoring some process using process table or some net snmp mib extention I can report that the service is down while it is just running! It is only the agent not responding.
When you use the SnmpMonitor to get a specific oid and a given value you just assert that there is a monitored service that depends on the snmp agent availability.
If the agent is down you are not aware of the Service Status.
Actually the SnmpMonitor when you got a null SnmpValue that means no response from Agent create a status unavailable. This is not true, instead is true if you are monitoring
the SNMP protocol it is not true when you are monitoring something elese using the SNMP protocol.
It seems to me that the status should be "unresponsive" in this case.
Of course that won't have any effect unless the poller config has
We suggest to set up a new parameter "ignore-unresponsive-agent" with a default value of
Maybe unknown is better then unresponsive!
This is a dependency trouble.