nagios-charmers team mailing list archive

[Drew Freiberger <1741540@xxxxxxxxxxxxxxxxxx>]

Just heard that an alert from a warning state on a site that cleared in
nagios but didn't get resolved automatically in pagerduty happened.

Suspect nagios upgrade/config change that might be causing resolved
status not to make it to pagerduty?

-- 
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/1741540

Title:
  pagerduty not getting resolved status when re-check performed via
  thruk

Status in Nagios Charm:
  New

Bug description:
  I've found lately that when a check is in critical state in
  nagios/thruk, and pagerduty has sent out an alert, if the issue is
  cleared by admin action and then one schedules a re-check of the
  service via thruk, it seems that pagerduty does not receive the OK
  status as a result of that check from thruk.

  This has been observed on the "incorrect number of ha routers" check
  via bootstack thruk.

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