nagios-charmers team mailing list archive

[Andrea Ieri <1718835@xxxxxxxxxxxxxxxxxx>]

pagerduty_nagios.pl puts new events in a queue, and periodically tries
to flush the queue by sending the events to the pagerduty service. If
errors prevent the queue from being flushed, the notification script
will retry until successful; however, if errors affect the enqueuing (as
per bug 1718833) the events are indeed lost.

Nagios does not unfortunately seem to be able to cache notifications if
the called script returns an error. I am therefore tentatively marking
this as won't fix as there's not too much we can do to work around this
limitation.

** Changed in: nagios-charm
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1718835

Title:
  pagerduty alerts are lost if pagerduty script is broken

Status in Nagios Charm:
  Won't Fix

Bug description:
  Using the current charm, on Xenial, when I setup a fresh unit and
  enable pagerduty, if I do something which causes an alert but the
  pagerduty script doesn't work (e.g. because of bug 1718833) then the
  alert is lost into the dark void of nowhere.  Maybe we're not doing
  something with queuing these alerts and checking return codes from the
  /usr/local/bin/pagerduty_nagios.pl script?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1718835/+subscriptions