Skip to content
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

nagiosplugin.state.Warn vs. nagiosplugin.state.Warning (considering nagiosplugin.state.Critical) #26

Open
ypid-geberit opened this issue Jul 16, 2020 · 1 comment
Assignees
Labels
feature New feature or request good first issue Good for newcomers trivial
Milestone

Comments

@ypid-geberit
Copy link

Hi,

I just stumbled across what I think is an inconsistency. Those states exist currently:

Ok
Warn
Critical
Unknown

I think this module should rather support Warning instead of Warn to comply with the exact wording used in the plugin API spec: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/pluginapi.html

Backwards compatibility with existing checks should be provided by still supporting Warn.

For background, I am using a statement like this getattr(nagiosplugin.state, nagios_state_string, nagiosplugin.state.Unknown) to use an already existing Nagios state (nagios_state_string) in a custom Context class.

What do you think?

@mpounsett
Copy link
Owner

That seems reasonable, and it would be a pretty simple change. I'll add it to the TODO list.

@mpounsett mpounsett self-assigned this Aug 1, 2020
@mpounsett mpounsett added feature New feature or request trivial labels Aug 1, 2020
@mpounsett mpounsett added this to the 1.3.3 milestone Aug 1, 2020
@mpounsett mpounsett added the good first issue Good for newcomers label Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request good first issue Good for newcomers trivial
Projects
None yet
Development

No branches or pull requests

2 participants