Lower nagios check for "offset" criticality to WARNING

Bug #1854068 reported by Ryan Farrell
14
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.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

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?

Revision history for this message
Xav Paice (xavpaice) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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