Alerting: Add CustomDetails field in PagerDuty contact point #64860
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
santihernandezc
added
area/alerting
santihernandezc
requested review from
sakjur,
papagian and
suntala
and removed request for
a team
yuri-tceretian
added
the
area/alerting/notifications
grafanabot
added
the
type/docs
brendamuir
reviewed
Mar 21, 2023
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
docs/sources/alerting/manage-notifications/manage-contact-points/configure-notifiers.md
Outdated
Show resolved
Hide resolved
…ernandezc/add_custom_details_to_pagerduty
santihernandezc
commented
Mar 28, 2023
docs/sources/alerting/manage-notifications/manage-contact-points/_index.md
Show resolved
Hide resolved
brendamuir
approved these changes
Mar 29, 2023
santihernandezc
deleted the
santihernandezc/add_custom_details_to_pagerduty
branch
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.
This PR adds support for
CustomDetailsin Grafana's PagerDuty notification channel. This field is an object containing arbitrary key-value pairs, currently available in external Alertmanagers but not when using Grafana's internal one.The details provided by the user get merged with the default ones we use to provide information about the notification. In case of duplicate keys, the user-defined details prevail.
This field is optional, and it uses the same UI elements we use in external Alertmanagers.
These values are rendered on PagerDuty as part of the notification details.
Related issue: #63604
Note: For this feature, we need functionality introduced in the latest commit (as of now) of the
grafana/alertingpackage, hence the update ingo.modandgo.sum