Heya Thank you for the fast answer.
> notification != eventhandler
Right.
>> Did I configure something wrong or has Icinga's behaviour changed?
>
> you have obviously abused an eventhandler for notifications.
Well, in fact this is what I want to do. The event handler calls a
script which tells our self-written application what happened. I am very
sure that this worked differently like a year ago with Nagios. I am not
sure about the time but I am sure that this was the case once back in
time :).
My configuration is:
Every host uses the same template which includes:
event_handler_enabled 1
event_handler notify-host
Then notify-host is defined as calling the script which inserts the data:
define command {
command_name notify-host
command_line <the command>
}
Same is true for services.
As notification is not done by Icinga in our setup I don't see another
solution than this one. But probably I am wrong - anyone? :)
Denis
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
