-
Notifications
You must be signed in to change notification settings - Fork 25k
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 > Pager Duty > Set Incident Urgency #67203
Comments
Pinging @elastic/es-core-features (Team:Core/Features) |
I'm removing the |
Pinging @elastic/es-data-management (Team:Data Management) |
This has been open for quite a while, and we haven't made much progress on this due to focus in other areas. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed. |
Describe the feature:
Currently, with the watcher > pagerduty integration, every incident that gets sent to pager duty is marked as
high
for it's urgencyIf you see here, there is no option for urgency: https://www.elastic.co/guide/en/elasticsearch/reference/current/actions-pagerduty.html
However if you see here: https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/~1incidents/post
The ability to set urgeny is available in their API.
Describe a specific use case for the feature:
We want all alerts to go to pagerduty, but we don't want them all being marked as high. We want to be able to triage this ourselves. This should be changeable.
The text was updated successfully, but these errors were encountered: