nagios-eventhandler-cachet icon indicating copy to clipboard operation
nagios-eventhandler-cachet copied to clipboard

A Nagios event handler to push Nagios notifications to Cachet API

Results 8 nagios-eventhandler-cachet issues
Sort by recently updated
recently updated
newest added

Hi, I have installed Cachet and try to push notification from Nagios to Cachet using event handlers. I'm getting the error **'Can't query components'** while running the below command **./cachet_notify...

Greetings, You have done a great job here! One issue here - when an identical incident repeats more than once the status change to "Fixed" is updated only for the...

I'm testing this eventhandler with cachethq v2.2.2 e.g. `/usr/lib64/nagios/plugins/eventhandlers/cachet_notify 'Whatever Web Access' 'My nagios service'` I get the following response: ``` CRITICAL HARD 'The service is Critical' KO HARD: creating...

…created with each new warning/critical Added a metric update option by using the event_handler in the following fashion: event_handler cachet_notify! -m=true The cachet_notify script checks for the presence of '-m=true'...

Hi, Tested and working when the status is critical and solved (operational) but if the status from nagios is partial outage my components stay indefinitely in partial outage status... I...

Currently using nagios-eventhandler-cachet with a cachet installation v2.0.0 RC5 When running the cachet_notify to change a component, it returns the correct task "KO HARD": ``` ./cachet_notify 'component' 'nagios service' CRITICAL...

It would be nice if we could get the $service_output variable attached to the component so one can hover over and use the "?" icon to see the current problem...

Currently everything is working alright....but if the component length is too long, the issue doesn't appear...how can this be configured?