Allows overriding notification settings per alert #168
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 fixes issue #76, allowing individual alerts to override some notification details (e.g. email recipient, Slack channel).
Example:
{ "name": "site-404s", "time_window": "10minute", "method": "maximum", "query": "...", "rules": ["warning: > 10"], "override": { "slack": { "channel": "#site-dev" }, "smtp": { "to": "dev-site@example.org" } } }Not all fields can be overridden, nor can all alert methods. Overrides usually don't let you change which server you're talking to, or what API key you're using. Available overrides:
commandroomurl,params,methodchannel,usernamesender,tourl,routing_key