Public bug reported:
We had an incident where the root disk of the nagios VM on an infra node
was marked read-only due to I/O Errors.
No checks ran after the i/o errors started and no alerts were sent to
pagerduty which was enabled on the site.
While the remote thruk-external-agent alerted to content issues on the
nagios/thruk unit, it would be nice if a site with pagerduty enabled
could have a watchdog process that alerts out if checks are not running
or if the filesystem is in read-only mode.
** Affects: charm-nagios
Importance: Undecided
Status: New
--
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/1908432
Title:
Nagios unit stops checks and doesn't alert when disk goes read-only
Status in Nagios Charm:
New
Bug description:
We had an incident where the root disk of the nagios VM on an infra
node was marked read-only due to I/O Errors.
No checks ran after the i/o errors started and no alerts were sent to
pagerduty which was enabled on the site.
While the remote thruk-external-agent alerted to content issues on the
nagios/thruk unit, it would be nice if a site with pagerduty enabled
could have a watchdog process that alerts out if checks are not
running or if the filesystem is in read-only mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nagios/+bug/1908432/+subscriptions
--
Mailing list: https://launchpad.net/~nagios-charmers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~nagios-charmers
More help : https://help.launchpad.net/ListHelp
