-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fix nagios parser to parse all perfdata and report info message. #5601
Merged
Merged
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
2d22208
Fix nagios parser to parse all perfdata and report info message.
ada4478
Use bytes.Buffer instead of strings.Builder.
232a2da
Use space instead of \n when concatenating the longmsg.
cf33a00
Use service_output, long_service_output names. Use '\n' concatenator.
eca9410
Append nagios status after parsing the output
6257c63
Fix failing tests when comparing maps
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I like injecting the return code into the parser data, is there a reason this needs to be changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like the
state
,service_output
,long_service_output
semantically belong together and should be a part of the same measurement.The current parser interface doesn't allow to pass any extra information to the parser, whilst the
service_output
and thelong_service_output
are known during the parsing time only.The parser will properly parse bytes for which the
nagios.AppendExitCode(...)
wasn't called, it will assume the default state to be 0.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not my primary concern but wouldn't the state be set incorrectly depending on how the output ends? Perhaps we could add the state to the
telegraf.Metric
after it has been returned from the parser?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we encode the state in the
exec
plugin, no matter how the output ends, the parser will always properly decode the state and strip those additional bytes.There might be an issue, when the parser is used somewhere else. And it is my bad, because I did not properly document the behavior of the
Parse
method. I will add the docs, but first, could you please comment on the next point:Appending the error code after we return from the parser is definitely possible. But will require me to do something like this:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danielnelson, what is your take on this ^^?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be sure, neither solution is great, and if I could do it over then I would probably make nagios it's own plugin separate from exec and scrap the standalone parser.
Putting that aside though, since I don't think it is worth a breaking change... I would parse, then if this is the NagiosParser, get the error code and iterate over the metrics looking for the
nagios_state
metric usingmetric.Name()
. You will also want to watch for the case where the state metric is not found, and add the field as a new metric.One more thing, could you do me a favor and use this form for adding the metrics?