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

Watcher: Allow defining PagerDuty severity field #34073

Open
Benny-Git opened this issue Sep 26, 2018 · 6 comments
Open

Watcher: Allow defining PagerDuty severity field #34073

Benny-Git opened this issue Sep 26, 2018 · 6 comments

Comments

@Benny-Git
Copy link

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.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@matt-davis-elastic
Copy link
Contributor

matt-davis-elastic commented Sep 26, 2019

Is this something that you are still dealing with? Have you found any work arounds?

@rjernst rjernst added the Team:Data Management Meta label for data/management team label May 4, 2020
@alexfrancoeur
Copy link

For those following this issue, our new alerting framework supports multiple PagerDuty severities and action types.

The action’s type: Trigger, Resolve, or Acknowledge.
The event’s severity: Info, warning, error, or critical.

For more details on the integration itself, check out the documentation here: https://www.elastic.co/guide/en/kibana/current/pagerduty-action-type.html

@runtman
Copy link

runtman commented Jan 5, 2021

This request is talking about watcher, you are talking about alerting & action which are different features.

Is watcher being phased out?

@gerardpeters
Copy link

Is this issue ever being resolved? I would like to send send events to pagerduty with a severity other than critical.

@runtman
Copy link

runtman commented Jan 26, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants