- Notifications
You must be signed in to change notification settings - Fork1.1k
Added a special DYNAMIC_SEVERITY tag which allows overriding a trigger severity#146
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
kgeorgiou-strike wants to merge1 commit intozabbix:masterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
+66 −0
Conversation
This file contains hidden or 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
…r severityThe severity can be changed by raising it by a certain amount, lowering it, or setting a newseverity. When trigger that fires has the "DYNAMIC_SEVERITY" tag (which could be coming fromthe template, host, trigger) the severity is set/adjusted according to the tag value.Where "+N" raises the severity by N, "-N" lowers it by N, and just "N" (no plus or minus)sets the severity to N. The "DYNAMIC_SEVERITY" tag can include macros so for example you canhave the ping trigger with the tag DYNAMIC_SEVERITY={$PING_SEVERITY} and set the macro to +1in production hosts.Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
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.
The severity can be changed by raising it by a certain amount, lowering it, or setting a new severity. When trigger that fires has the "DYNAMIC_SEVERITY" tag (which could be coming from the template, host, trigger) the severity is set/adjusted according to the tag value. Where "+N" raises the severity by N, "-N" lowers it by N, and just "N" (no plus or minus) sets the severity to N. The "DYNAMIC_SEVERITY" tag can include macros so for example you can have the ping trigger with the tag DYNAMIC_SEVERITY={$PING_SEVERITY} and set the macro to +1 in production hosts.
This is mostly here to start a discussion on how to get some form of dynamic severity levels implemented.