Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

added perfdata #18

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

added perfdata #18

wants to merge 1 commit into from

Conversation

dgoetz
Copy link

@dgoetz dgoetz commented Jul 13, 2015

Hello,

I have added perfdata to the plugin output. I think this should be default, but if you think perfdata should be optional let me know and I will add a parameter for enabling/disabling.

Regards,
Dirk

@@ -332,17 +332,20 @@ class YumTester:
if number_updates == 0:
status = OK
message = "0 Updates Available"
perfdata = "updates=0"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this (and following) should rather read something like "non-security-updates=" or so - otherwise it's ambiguous whether or not this number includes security updates.

@calestyo
Copy link
Owner

Hey.

Sorry for having ignored this for so long… well I'm basically in ultra-low-maintenance mode of check_yum ;-)

As for your pull request,... I have nothing against adding perf-data, neither against having it on per default.

  • But I do think there should be an option to disable it.
  • Further I made some first comments on your code…

Cheers,
Chris

@calestyo
Copy link
Owner

I've looked at this again,... first we should consider https://www.monitoring-plugins.org/doc/guidelines.html#AEN201

Second, I think:
Whenever --all-updates is used, then check_yum doesn't differentiate between security/non-security updates.
So we should actually have three possible perfdata values that may appear:
updates=total number of updates
security-update=security updates, if separately determined
non-security-update=non-security updates, if separately determined

Further, I've checked the checks from monitoring-plugins.org, well at least check_load,... and it doesn't contain an option to disable the perfdata,... so I think we don't need either.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants