Dear Team,
We are monitoring Links & Routers through Nagios, we changed the monitoring time for Links as 15 mins polling interval, 15 mins recheck interval & 3 check attempts and monitoring time is 11:00 to 16:00.
we took the report of flapping Links, when checked the details of single flapping link in host details, it was up since 20 hours. have below 2 questions regarding this.
1. If it is up since 20hours then why its still in Flapping state?
2. As we have set monitoring time as 11:00 to 16:00, will the Host up state includes the duration b/w 16:00 to 10:00 ( non monitoring period )
Please help in this regard.
Regards,
Flapping & Monitoring Time
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Flapping & Monitoring Time
Without going through your logs, most likely it is in an up flapping state because it is failing one check every once in a while, but not enough to actually go into a warning\critical\down state, thus flapping as there are potentially intermittent checks failing. It is perfectly normal for nagios to put something in a flapping state when this is the case.
As for uptime, nagios does not remove non-monitored time from the total uptime. Along those lines, it also does not remove downtime from that counter either. Regarless of either of those mentioned states, if nagios has a host\service in a particular state and it stops monitoring intentionally, it will continue to count that host\service as having that same state throughout the length of time until the next check that would cause a state change. Were you expecting different behavior? If so what did you intend to see here instead?
As for uptime, nagios does not remove non-monitored time from the total uptime. Along those lines, it also does not remove downtime from that counter either. Regarless of either of those mentioned states, if nagios has a host\service in a particular state and it stops monitoring intentionally, it will continue to count that host\service as having that same state throughout the length of time until the next check that would cause a state change. Were you expecting different behavior? If so what did you intend to see here instead?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
-
wiproltdwiv
- Posts: 281
- Joined: Sat Sep 08, 2012 12:52 am
Re: Flapping & Monitoring Time
Dear Team,
Thanks for the clarity, if this is the case for non monitoring period. then please suggest how will it link to Legacy Availability report ??
suppose we've set the monitoring time 11:00 to 16:00, and if we are extracting report for the same time period through Legacy then whether the non monitored time host/service up/down states will be included in the report or not.
because if a host goes down before the monitoring stops, then down percentage will be more in the report.
Please suggest in this regard
Thanks for the clarity, if this is the case for non monitoring period. then please suggest how will it link to Legacy Availability report ??
suppose we've set the monitoring time 11:00 to 16:00, and if we are extracting report for the same time period through Legacy then whether the non monitored time host/service up/down states will be included in the report or not.
because if a host goes down before the monitoring stops, then down percentage will be more in the report.
Please suggest in this regard
You do not have the required permissions to view the files attached to this post.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Flapping & Monitoring Time
As sreinhardt said above, if a host goes go into a down state before your "monitoring time" stops, it will show it as down in the report. It won't try to hide, or mask that fact from you, or anyone else who might be viewing your report, as the host was truly down at that point.