Added 'stalking_notify' logic for both Host and Service based objects #981
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
…fication' as well as 'next_notification' validations for both hosts and services
Rfferrao87
force-pushed
the
605-stalking-notify-feature
branch
from
7b40e7f
to
70afe93
Compare
|
@ericloyd what do you think here? |
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.
Implements #605 when both
stalking_optionsandstalking_notifyare enabled in either host and/or service definitions; its functionality is similar to theis_volatiledirective, except with a more granular approach, as it only emits notifications for the states covered bystalking_optionsand also only if the check output changes.