New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_icmp 'loses' perfdata labels on DOWN/CRITICAL #510
Comments
Good catch - you're right that the performance data tags shouldn't change based on plugin status. I've added this for the next bugfix release |
sawolf
added a commit
to sawolf/nagios-plugins
that referenced
this issue
Jan 14, 2020
… packet loss is at 100%
sawolf
added a commit
to sawolf/nagios-plugins
that referenced
this issue
Jan 14, 2020
… packet loss is at 100%
The fix turned out to be relatively simple, so if you're willing to compile the plugin manually, check the branch linked in the pull request above. |
Tried it out, works. |
sawolf
added a commit
that referenced
this issue
Feb 17, 2020
Fix #510 - perfdata tags should remain the same even if packet loss is at 100%
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using check_icmp for checks on hosts/services the checks perfdata output changes based on the state, which is a problem for the old pnp4nagios graphing tool.
Check that reports ok/up:
Check that reports critical/down:
This results in the graph for packets lost containing rta ms values instead of the pl % ones:
pnp4nagios is not set up to have multiple files for the perfdata, as this is not suitable for the setup.
I would like to propose that check_icmp retains the other perfdata labels in the critical/down output and fills them with the warning/critical values (like check_ping does) or just zero..
system is CentOS 7, Plugin Version is check_icmp v2.2.1.git (nagios-plugins 2.2.1)
The check_icmp plugin (on Ubuntu) for the monitoring-plugins project does not have this problem
The text was updated successfully, but these errors were encountered: