Introduction

Configure how targets should be monitored and how users are notified upon their failure. In addition you can specify if traps, syslog or discovery events should be discarded or forwarded. For discovery events you can define a coarse alert policy with the "notify" string and thresholds (CPU, Mem etc.) in nedi.conf. They can be overridden here for each target.

Usage

Traps or syslog messages of nodes or devices not added to monitoring will only create "other" (level 10) events.

The actual polling is done by moni.pl which should be started automatically. It also relies on nedi.conf (can be edited in System-Files), where you can set the pause between polls, how many tests a device can fail before it is marked down and how emails should be sent.

If a target is reported to be down an incident is created with the start time set to the time it's detected at. The end time will be added automatically, when the target is responding again.

This daemon can be stopped and started from System-Services after changing any settings to quickly see the results. Otherwhise you'll have to wait until the next polling cycle starts.

A shaded background indicates that the target is not found as node or device anymore.

Message Flows

Details