nagios-charmers team mailing list archive

[Eric Chen <1834818@xxxxxxxxxxxxxxxxxx>]

This issue was pending over years. NRPE charm will be deprecated soon.
Therefore, we won't implement this feature. But if there is big impact
for the daily work, please welcome to open it and escalate the priority.
thanks

** Changed in: charm-nagios
     Assignee: James Hebden (ec0) => (unassigned)

** Changed in: charm-nagios
       Status: Triaged => 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/1834818

Title:
  Nagios warnings should be sent to pagerduty as low-urgency events

Status in Nagios Charm:
  Won't Fix

Bug description:
  Given different alerting policies and routing can be configured in
  PagerDuty for low-urgency alerts, it is expected that low-urgency
  events like Nagios warnings would be configurable to only notify users
  during business hours or other periods where they would be more
  amenable to being paged for such a warning.

  Currently, all notifications from Nagios, whether they be warnings or
  critical alerts, are assigned high-urgency in PagerDuty. This does not
  reconcile well with user expectation - to better support PagerDuty's
  intended event routing, we should send warnings to PagerDuty as low-
  urgency events. This would provide a better user experience and better
  reconcile user expectation with charm behaviour.

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