Notify Me of Important Events
Triggers define criteria upon which the trigger is executed, but a Trigger does not cause any action to take place. These criteria cover nearly every aspect of monitoring and are extremely flexible, and are available via drop-down boxes. To add additional criteria, either select the plus icon, or the branching icon at the right of each line. The most basic criteria that a beginning Zenoss administrator will probably look at are Production State, and Severity. A good first basic trigger is to activate on any event that has a Critical Severity on a Production device.
Notifications are actions taken when the criteria for a Trigger is met, and that trigger is activated. To associate a Notification with a Trigger, after creating the Trigger, open it, and select the Triggers from the drop-down box in the "Notification" tab.
Zenoss supports 4 types of notifications:
In Prepare_Remote_Device we discussed SSH keys, and with a command plugin we can run remote scripts or attempt to restart services via ssh. This is also where the "count" criteria in Triggers comes in handy. If an attempt to restart a service fails several times, we can then escalate by adding a "count" criteria to a second notification and let someone know that the service is down and won't restart. Commands are specified in the "Content" tab of the Notification.
The E-mail tab allows a formatted e-mail with event information to be sent. The body of the message can be modified in the "Content" tab, and the recipients specified in the "Subscribers" tab. A test event e-mail is reproduced below, the last four lines are links to your Zenoss instance.
Device: localhost Component: /Status/Ping Severity: 5 Time: 2013/03/24 17:51:58.000 Message: Purple! Event Detail Acknowledge Close Device Events
This isn't used much anymore, but for those of you who still own pagers, this plugin is available to interface with your pager.
SNMP Traps Notifications can be sent to an existing legacy NMS for additional handling, routing, and escalation.