You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pagerduty2 event handler can be used via the alert rule builder if you use the handler's default routing key. However, if you need to customize the routing key for your alert you have to edit the tickscript. This means you lose all the nice features of the alert rule builder.
Some other event handlers let you customize their destination without dropping down to tickscript. The email handler, for example, lets you configure the destination email address. It would be helpful if the pagerduty2 event handler let you customize the pagerduty2 routing key in a similar way.
Ideally it would be possible in the pagerduty2 event handler config to define a list of routing keys and assign identifiers to them. Then in the alert rule builder, it could be possible to choose from one of those identifiers.
However, simply exposing a text field in the alert rule builder where someone could type a routing key would be a huge improvement.
The text was updated successfully, but these errors were encountered:
sciurus
changed the title
Support changing the pagerdutyv2 routing key in the alert rule builder
Support changing the pagerduty2 routing key in the alert rule builder
Jan 14, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Feel free to reopen if this issue is still important to you. Thank you for your contributions.
The pagerduty2 event handler can be used via the alert rule builder if you use the handler's default routing key. However, if you need to customize the routing key for your alert you have to edit the tickscript. This means you lose all the nice features of the alert rule builder.
Some other event handlers let you customize their destination without dropping down to tickscript. The email handler, for example, lets you configure the destination email address. It would be helpful if the pagerduty2 event handler let you customize the pagerduty2 routing key in a similar way.
Ideally it would be possible in the pagerduty2 event handler config to define a list of routing keys and assign identifiers to them. Then in the alert rule builder, it could be possible to choose from one of those identifiers.
However, simply exposing a text field in the alert rule builder where someone could type a routing key would be a huge improvement.
The text was updated successfully, but these errors were encountered: