Hi I am new to both Nagios Core and Nagios XI and we are currently running both in our environment with the goal being to migrate everything from Core over to XI. In the meanwhile I have a customer who would like to set a hard limit for RTA in Nagiosgraph to 600 milliseconds because he is only interested in RTA's of 600 and under. The default has a y-axis (milliseconds) that shows 0.2 - 1.4. I would like to change that range to 0.0 - 0.6. Does anyone know how I can do that? All of the research I have done says to edit rrdopts.conf and then uncomment the reference to that file in nagiosgraph.conf. But I haven't be able to find any examples of what entries I would put in rrdopts.conf to make these changes. Can anyone point me in the direction of how to edit this successfully?
Thanks.
Edit milliseconds (y-axis) range for rta in Nagiosgraph
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Edit milliseconds (y-axis) range for rta in Nagiosgraph
I want to understand if you are wanting to change the thresholds or just the pretty graphs?
Nagios XI uses check_icmp for ping checks. A standard used is:
./check_icmp -H ip_address -w 3000.0,80% -c 5000.0,100% -p 5
So -p 5 means 5 packets will be sent.
For warning, threshold is more than 3000ms RTT OR more than 80% loss of packets sent.
For critical, threshold is more than 5000ms RTT OR more than 100% loss of packets sent.
If warning and critical thresholds are not defined, they will default to:
warning = 200,40%
critical = 500,80%
How does this compare to your ping checks for your hosts?
Nagios XI uses check_icmp for ping checks. A standard used is:
./check_icmp -H ip_address -w 3000.0,80% -c 5000.0,100% -p 5
So -p 5 means 5 packets will be sent.
For warning, threshold is more than 3000ms RTT OR more than 80% loss of packets sent.
For critical, threshold is more than 5000ms RTT OR more than 100% loss of packets sent.
If warning and critical thresholds are not defined, they will default to:
warning = 200,40%
critical = 500,80%
How does this compare to your ping checks for your hosts?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Edit milliseconds (y-axis) range for rta in Nagiosgraph
More interested in just changing the pretty graphs. Specifically looking at Nagiosgraph in Nagios Core. In that case I see 2 graphs for each day, week, month and year. The 2 graphs chart either packet loss or round trip average. I am interested in how I can change the y-axis range for the round trip average graph. Currently the range shown is 0.2 - 1.4 (in milliseconds) and I would like to change that so that the range shown is 0.0 - 0.6 instead.
Re: Edit milliseconds (y-axis) range for rta in Nagiosgraph
I found this on the Nagiosgraph discussion site, is this what you are looking for?
It describes setting the upper and lower limits for the graphs.
http://sourceforge.net/p/nagiosgraph/di ... /51e9348d/
It describes setting the upper and lower limits for the graphs.
http://sourceforge.net/p/nagiosgraph/di ... /51e9348d/
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Edit milliseconds (y-axis) range for rta in Nagiosgraph
Yes that is what I want to do and that is good information. But the problem is that I don't know what service I would be setting the upper and lower limits on. From my research I believe it is probably check_ping. But I don't believe that I could just set check_ping=-u 0.6 -l 0.0 -r because that service reports on more than just rta, it also reports on packet loss. So I would have to somehow determine how to tell it that I wanted to set the u and l limit for rta and leave the packet loss part unchanged. I've tried searching the Internet as much as possible but just don't know where else to look to find any detailed information on this- any suggestions would be greatly appreciated.
Re: Edit milliseconds (y-axis) range for rta in Nagiosgraph
I did a little searching myself and there isn't much for examples. It does look like the setting the limits will affect all of the data so try it out and see if it is good enough.
Other than that, you would have to setup separate graphs and scale those to what you need.
Other than that, you would have to setup separate graphs and scale those to what you need.
Be sure to check out our Knowledgebase for helpful articles and solutions!