-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Watcher: Allow defining PagerDuty severity field #34073
Comments
Pinging @elastic/es-core-infra |
Is this something that you are still dealing with? Have you found any work arounds? |
For those following this issue, our new alerting framework supports multiple PagerDuty severities and action types.
For more details on the integration itself, check out the documentation here: https://www.elastic.co/guide/en/kibana/current/pagerduty-action-type.html |
This request is talking about watcher, you are talking about alerting & action which are different features. Is watcher being phased out? |
Is this issue ever being resolved? I would like to send send events to pagerduty with a severity other than critical. |
I create event rules within pagerduty to get around it, not the solution but something that kept it ticking whilst this hopefully gets worked on |
Describe the feature:
After switching to PagerDuty API V2 ( #32243, #32285), I would like to have the ability to set the severity of a PagerDuty event.
This is currently hard coded to "critical", which would result in PagerDuty ringing my phone in the middle of the night, if Watcher detects a slight increase in our load.
The text was updated successfully, but these errors were encountered: