Add Pagerduty severity for workflows #93
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
cpanato
reviewed
Jul 25, 2023
bobcallaway
previously approved these changes
Jul 25, 2023
Staging workflows will be low priority (warning), and production will be high priority (error). Rate limiting will be low priority since it's not something critical to respond to. Signed-off-by: Hayden Blauzvern <[email protected]>
haydentherapper
force-pushed
the
severity
branch
from
5c4120c
to
ab94d58
Compare
|
I can use Event Orchestration rules in Pagerduty to dynamically change severity for staging events over the weekend, so this PR should be good to go. |
|
Don't think I need this, going to use |
bobcallaway
approved these changes
Jul 25, 2023
|
Not needed, we'll use |
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.
Staging workflows will be low priority (warning), and production will be high priority (error). Rate limiting will be low priority since it's not something critical to respond to.
Ref https://github.com/sigstore/public-good-instance/issues/1568
Summary
Release Note
Documentation