This ZenPack adds new event notification actions that are used by the
zenactiond
daemon.
The Event Forwarder action forwards events to the eventForwarder rabbit queue. Destination extension packs, such as ZenPacks.SteelHouseLabs.SplunkForwarder and ZenPacks.SteelHouseLabs.ZenossForwarder, can then consume this queue and process events to their appropriate destination.
Prerequisite | Restriction |
---|---|
Product | Zenoss 4.1.1 or higher |
Required ZenPacks | None |
Other dependencies | pika 0.98 |
These notification actions are not able to provide immediate feedback as to
whether or not configuration information is correct, so the zenactiond.log
file must be checked to ensure that the actions are working correctly.
See the Zenoss Service Dynamics Administration Guide for more information about
triggers and notifications. Any issues detected during the run of the
notification will result in an event sent to the event console as well as a
message in the zenactiond.log
file.
This assumes that the appropriate triggers have already been set up.
- Navigate to
Events
->Triggers
page. - Click on the
Notifications
menu item. - Click on the plus sign ('+') to add a new notification.
- From the dialog box, specify the name of the notification and select the
Event Forwarder
action. - Enable the notification and add a trigger to be associated with this action.
- Click on the
Submit
button.
Install the ZenPack via the command line and restart Zenoss:
zenpack --install ZenPacks.SteelHouseLabs.EventForwarder-<version>.egg zenoss restart
To remove the ZenPack, use the following command:
zenpack --remove ZenPacks.SteelHouseLabs.EventForwarder zenoss restart
The Zenoss support team will need the following output:
- Set the
zenhub
daemon intoDEBUG
level logging by typingzenhub debug
from the command-line. This will ensure that we can see the incoming event in thezenhub.log
file. - Set the
zenactiond
daemon intoDEBUG
level logging by typingzenactiond debug
from the command-line. This will ensure that we can see the incoming notification request and processing activity in thezenactiond.log
file. - Create an event from the remote source, by the
zensendevent
command or by the event consoleAdd an Event
button. This event must match the trigger definition that will invoke your notification action. - Verify that the event was processed by the
zenhub
daemon by examining thezenhub.log
file. - Wait for the
zenactiond
daemon to receive and then process the notification request. - In the case of errors an event will be generated and sent to the event console.
- Running rabbitmqctl -p /zenoss list_queues should show a 'eventForwarder' queue once after the Notification is enabled on the Triggers -> Notifications page.
Type | Name |
---|---|
Notification | zenactiond |