Pagerduty alert fixes for SRE agent demos#4
Open
paulyuk wants to merge 2 commits into
Open
Conversation
… for PagerDuty incident management.
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
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.
This pull request introduces enhancements to incident management processes and automation scripts. Key changes include the addition of detailed mitigation steps for handling 500 errors in the
sreagent-500errors.prompt.mdfile and updates to thecreate-pagerduty-incident.shscript to improve incident creation with priority handling and timestamped titles.Enhancements to incident response:
.github/prompts/sreagent-500errors.prompt.md: Added a detailed prompt for handling incidents related to 500 errors, including step-by-step instructions for mitigation, correlation analysis, and reporting.Improvements to PagerDuty integration:
.github/scripts/create-pagerduty-incident.sh: Added support for specifyingPAGERDUTY_PRIORITY_IDas an optional environment variable, defaulting toP28K36Rfor P1 incidents. [1] [2].github/scripts/create-pagerduty-incident.sh: Enhanced logging to include the priority ID in the output parameters..github/scripts/create-pagerduty-incident.sh: Updated the incident title to include a timestamp for better traceability..github/scripts/create-pagerduty-incident.sh: Modified the JSON payload to include the priority ID when creating PagerDuty incidents.