docs(observability): show enriched PagerDuty context fields in the template#7124
Merged
Merged
Conversation
…mplate client/group/class + a details map give the incident real context beyond the bare summary (which deployment paged, which alert rule, the runbook/description annotations, how many instances are firing) -- matches what's actually live on edge-nl-01 for #5009. Also notes that PagerDuty's "Priority" (P1-P5) isn't a pagerduty_config field -- that's PagerDuty's own Event Orchestration feature, configured on their side.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
loopover-orb
Bot
added
the
gittensor:bug
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.
Summary
`client`/`group`/`class` + a `details` map give the incident real context beyond the bare summary (which deployment paged, which alert rule, the runbook/description annotations, how many instances are firing) -- matches what's actually live on edge-nl-01 for #5009.
Also notes that PagerDuty's "Priority" (P1-P5) isn't a `pagerduty_config` field -- that's PagerDuty's own Event Orchestration feature, configured on their side, not Alertmanager's.
Test plan