Hi all,
I just commit the code/test/doc of a new feature of the "lazy admin" release
: the notification ways :)
*The Notification Ways :*
It's use to manage with more control the notification commands used for
contacts. Let take an example : you want email notification 24x7 but SMS
only the night and for critical alerts only. How do this with contacts
definitions? You have to duplicate the contact. One with notification_period
of 24x7 and the email command, and one other with send-by-sms for the night.
Duplicate contacts can be hard to manage in services definitions afterward.
That why notification ways are useful : you defined some notification ways
(that look really like contacts) and you linked them to your contact. For
example, you can have the below configuration :
define contact{
contact_name test_contact
alias test_contact_alias
email nob...@localhost
can_submit_commands 1
notificationways email_in_day,sms_the_night
}
#Email the whole 24x7 is ok
define notificationway{
notificationway_name email_in_day
service_notification_period 24x7
host_notification_period 24x7
service_notification_options w,u,c,r,f
host_notification_options d,u,r,f,s
service_notification_commands notify-service
host_notification_commands notify-host
}
#But SMS only the night
define notificationway{
notificationway_name sms_the_night
service_notification_period night
host_notification_period night
service_notification_options c
host_notification_options d
service_notification_commands notify-service-sms
host_notification_commands notify-host-sms
}
The contact is valid because he's got valid notificationways. For each
notification, we ask for all notification_ways to give us the commands to
send. If their notification options or timeperiod is not good, they just do
not give one.
Of course, you can still have "old school" contact definition, and even with
the notificationways parameters. The service_notification_period parameter
of the contact will just be used to create a notificationways like the
others, that's all.
*Should we rename this parameter ?*
One question : should we let the name as notificationway or we should rename
it as notification_way ?
*And now?*
Now, we will focus a little to some feature ware are missing from nagios:
*Timezone option
*Timeperiod inheritance (use of use :) )
*Detect and correct time shifting
*Log rotation and archive
*syslog logging (will be a new broker module, so will be easy)
*Raise _NAGIOS environment macros.
*Allow to not inherit dependencies (but why do not inherit them in fact?)
*Illegal macro characters
Nothing really hard I think, but it should be done.
This will be surely done for the 0.4 release. The 0.3 is quite advanced, and
I think the only thing we miss is the demo VM :)
If someone want to take a ticket at
https://sourceforge.net/apps/trac/shinken/report/2 you can :)
Jean
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
