Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support changing the pagerduty2 routing key in the alert rule builder #5038

Closed
sciurus opened this issue Jan 14, 2019 · 3 comments
Closed

Support changing the pagerduty2 routing key in the alert rule builder #5038

sciurus opened this issue Jan 14, 2019 · 3 comments
Labels

Comments

@sciurus
Copy link

sciurus commented Jan 14, 2019

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.

@sciurus 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
@nevins-b
Copy link

nevins-b commented Mar 6, 2019

We ran into this recently as well. Even if there is now routing key set in the configuration we aren't able to supply one as part of alert creation.

@stale
Copy link

stale bot commented Jul 22, 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.

@stale stale bot added the stale label Jul 22, 2019
@stale
Copy link

stale bot commented Jul 29, 2019

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.

@stale stale bot closed this as completed Jul 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants