-
Notifications
You must be signed in to change notification settings - Fork 0
Home
This is the code of EyesOfNetwork advanced notifier.
The goal of this service is to substitute to nagios internal notifier.
All functionnality are most configurable than default nagios notification system.
Version 2.1 released with notification tracking.
This version will introduce a change on rules declarations.
This change affect the contact field in rules configurations.
Now, to you'll specify not the contact email, but the contact login.
Command change too. you'll need to specify a new field in command (-M) to give contact mail informations to notifier.
The previously field for contact email (-C) going contact name.
The new release v2.1 include notifications tracking.
Typically, current notification traited by notifier can check previous sent notification method to automatically adapt methods to use on it.
Exemple 1 :
- 1st notification sent DOWN on host with method email and sms.
- 2nd notification sent UP on host with normal notification only email. But if you choose to track these types (In rules), this method can be adapted to auto take same notifications than 1st (email and sms). Next to, if you re-send UP notification in exact same case (contact and host), the new notification take normal methos (email)
- Introduce in release v2.1 a new field in notifier.rules configuration line in end of line. This field manage notification tracking or not.
- 0 == tracking disables
- 1 == tracking enabled
- VERY IMPORTANT : all notifications command (in notifier.cfg) MUST BE in standard format if you use specific notification with match on state !
- Example if you have a specific command to send custom email on CRITICAL state, the command must be in format « command-nameSTATE ». You choose all name of « command-name » but the ending is compulsory in tune with nagios state. (See notifier.cfg for explicit examples)
On versions greater than 2.0, you must ensure than database is created before using notifier.