nagios-charmers team mailing list archive

[James Hebden <1902142@xxxxxxxxxxxxxxxxxx>]

"Tell me, Mr. Anderson. What good is a phone call, if you're unable...
to speak?"

Joke aside... perhaps it would be good to update the documentation
whilst adding this check to strongly encourage people to have more than
one form of alerting.

I'll also make a note to add email + SNMP traps to alertsync [0]

[0] https://launchpad.net/alertsync

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

Title:
  Nagios check for unreachable pagerduty

Status in Nagios Charm:
  New

Bug description:
  if enable_pagerduty=True, but nagios cannot reach pagerduty, there
  should be a new CRITICAL alert that pagerduty isn't reachable.

  Be sure to attempt to reach pagerduty through whatever proxies
  nagios+pagerduty services are configured with.

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