Public bug reported:
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?
** Affects: nagios-charm
Importance: Undecided
Status: New
** Tags: canonical-bootstack
--
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:
New
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
--
Mailing list: https://launchpad.net/~nagios-charmers
Post to : nagios-charmers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nagios-charmers
More help : https://help.launchpad.net/ListHelp
