feat: add opsgenie priority template based on severity label#3870
Closed
ncrmro wants to merge 1 commit intoprometheus:mainfrom
Closed
feat: add opsgenie priority template based on severity label#3870ncrmro wants to merge 1 commit intoprometheus:mainfrom
ncrmro wants to merge 1 commit intoprometheus:mainfrom
Conversation
Signed-off-by: Nicholas Romero <ncrmro@gmail.com>
ncrmro
changed the title
Collaborator
|
Hi! 👋 Thanks for opening this PR. As mentioned here, I think the same applies to
Why not use a custom template to set the priority field in Opsgenie for your use case? |
Author
|
@grobinson-grafana we did just that! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
P1 in my opinion is reserved for actual outage, in our case if cloudflare fails the external domain health check though I'm open to updating this default.