Managing traps for non-snmp enabled devices

[andersw]

Sorry for double posting, but I sent this to NSTI list yesterday before I realized that NSTI was a separate component.

I would like to use Nagios to monitor availability and battery status of a large group of "sensors" that do not speak SNMP. I've created a custom MIB which contains a SNMP table (each row represents a sensor) and a couple of traps for low battery etc. The MIB is implemented by a custom agent on a central server knows the current status of all the sensors.

Querying the SNMP table works great and so does sending traps. But the traps are not very useful in Nagios because they all originate from the same host (the central server). This means that I cannot acknowledge a low battery trap for a specific sensor etc.

All traps contain the sensor unique serial number in a varbind, which I assumed could be used to correlate the traps somehow without having to configure a host and service for each sensor.

Has anybody done something similar? Is Nagios the right choice for me or should I look into other options?

[abrist]

If you could set up each sensor as a separate service, you should be able to acknowledge and notify on a per-service basis.