Nagios Charm

Nagios unit stops checks and doesn't alert when disk goes read-only

Bug #1908432 reported by Drew Freiberger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nagios Charm
Won't Fix
Medium
Unassigned

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.

Tags: bseng-484
Edin S (exsdev)
Changed in charm-nagios:
importance: Undecided → High
Eric Chen (eric-chen)
tags: added: bseng-484
Eric Chen (eric-chen)
Changed in charm-nagios:
importance: High → Medium
Revision history for this message
Eric Chen (eric-chen) wrote :

This charm is no longer being actively maintained. Please consider using the new Canonical Observability Stack instead.
(https://charmhub.io/topics/canonical-observability-stack)
I will close this issue

Changed in charm-nagios:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.