Lower nagios check for "offset" criticality to WARNING
Bug #1854068 reported by
Ryan Farrell
This bug report is a duplicate of:
Bug #1839238: ntpmon should handle nan offset as unknown and not as critical.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NTP Charm |
New
|
Undecided
|
Unassigned |
Bug Description
During some transient behavior on a customer cloud we were inundated with CRITICAL alerts against NTP Offset: "offset is out of range (nan) - must be between -0.050000 and 0.050000".
These alerts did not result in any other apparent degraded behavior for other applications and we believe that we can lower the criticality of these particular messages to WARNING, instead of CRITICAL.
To post a comment you must log in.
I think the +/- 0.05 makes sense - it's lined up with when Ceph would start warning.
If we do want to have a Warning set and then an Critical set that would make sense to me.
It could be warning at 0.05 and then critical at say .25?