WIP: Support Nagios passive checks #29
Closed
Conversation
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 has been open for over a year now and is still marked as a work-in-progress, and lacks documentation. Closing for now. If you come back to this and manage to complete it, feel free to re-open this or issue a new PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is still WIP. Docs are missing. I will come back to this when I worked on some prerequisites and had time to test this. I will rebase the commits to keep them clean (remove the WIP from the message).
Feedback is already welcome.
One open question is how we should sanitize newlines in the output as they are not supported by most passive check implementations. I would suggest a
;for now.Closes: #27