It does not affect the in_ave_pct/out_ave_pct perfdata output. Both of these changes may disrupt your perfdata graphing if you use PNP4Nagios (RRD). This release changes the units for the in_ave/out_ave perfdata from bits (if you specify bits on the command line) to Bytes and changes inAbsolut/outAbsolut from Bytes to Continuous. These have been addressed in this release. 76: Thanks to Mark Rittinghaus for pointing out and recommending solutions to a couple of bugs in the perfdata. Times over Thresh - Counts and displays how many times the critical threshold was crossed during the graphed period. Min over Thresh - Displays how much time during the graphed period traffic was above the critical threshold.ħ. Total Bytes - Displays the total amount of data that has crossed the interface during the graphed period.Ħ. Rem Ave Cap - Calculates remaining capacity or headroom (how much bandwidth is left between your average traffic and your critical threshold).ĥ. Rem Peak Cap - Calculates remaining capacity or headroom (how much bandwidth is left between your peak traffic and your critical threshold).Ĥ. Peak - Prints the timestamp of when your peak traffic during the graph period happened.ģ. It converts the performance data from the Nagios plugin standard (Bytes) to bits, however, the graph is percent based, bits are listed in the text of the legend not on the graph itself.Ģ. Put this file in the /usr/local/pnp4nagios/share/templates/ directory. I also uploaded a PNP4Nagios template for the plugin. I simply fixed some code comments (spelling errors, removed spurious comments, etc.) 77: There are no functionality changes with this release. Some math issues found in check_iftraffic3 were resolved as well. See examples below for how to use the force switch.Ĭheck_iftraffic64 is an updated version of (check_iftraffic3) and has been changed to use 64 bit SNMP counters but can still handle 32 bit. Setting the check to force 32 or 64 will prevent this from affecting your results negatively in those cases. In cases where the 64 bit SNMP query doesn't always respond (but does sometimes) you will get mixed results (64 bit results last check 32 bit this check) and your output will be nonsensical (over 100%). By default, check_iftraffic64 auto detects between 32 and 64 bit counters, trying 64 bit first. I don't know if this will resolve everyone’s issue but if Rafael is right then this should address most if not all of the over 100% utilization scenarios. Several reviewers have posted this problem but I did not understand what was happening until Rafael van den Berg helped me see the cause, thanks Rafael. Alert: If you are having problems with results sometimes returning higher than 100% IN or OUT utilization try setting the check command to forced 32 or 64 bit mode with the -force switch.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |