pagerduty_configs.details does not respect event api v2

113 views

Skip to first unread message

Tigran

unread,

Feb 5, 2021, 5:08:18 AM2/5/21

to Prometheus Users

Hello,

I would like to customize details field inside pagerduty_configs inside alertmanager-config.yaml file but I realize that it does not allow more than 1 level of deep.

source: https://prometheus.io/docs/alerting/latest/configuration/#pagerduty_config

As you can see the details only allows <string: tmpl_string> and by default firing and resolved expand to a simple string https://github.com/prometheus/alertmanager/template/default.tmpl#L7

On the other hand, pagerduty event api v2 custom_details is declared as an Object, so a nested structure is not forbidden.

source: https://developer.pagerduty.com/docs/events-api-v2/trigger-events/#parameters

I believe this is an issue as it introduce useless complexity on pagerduty side. Most of the information carried by an alert comes from it's labels and instead of a nice json we have to use regex matchers to route correctly an alert to a service. With more rules more resources are used. With more than 1000 of applications, managing rules is a nightmare even with automation.