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

Add support for Pager Duty dynamic severity feature #1153

Closed
oscarmparedes opened this issue Nov 9, 2023 · 2 comments
Closed

Add support for Pager Duty dynamic severity feature #1153

oscarmparedes opened this issue Nov 9, 2023 · 2 comments

Comments

@oscarmparedes
Copy link

oscarmparedes commented Nov 9, 2023

Hi team,

I would like to request the pager duty integration to support dynamic severity from pager duty. Right now, the payload severity is sent in capital letters and the api v2 does not understand.

"Severity": "CRITICAL"
{"errors":["'payload.severity' is invalid (must be one of the following: 'critical', 'warning', 'error' or 'info')"],"message":"Event object is invalid","status":"invalid event"}%
{"errors":["'payload.severity' is missing or blank"],"message":"Event object is invalid","status":"invalid event"}%
https://support.pagerduty.com/docs/dynamic-notifications#eventalert-severity-levels

So Severity should be severity and WARNING should be warning. I think this should not be too difficult to change and it adds a great feature, avoid your team to wake up to all alerts vs managing all alerts from pager duty and waking up to just meaningful ones, without filtering on source.

@oscarmparedes
Copy link
Author

Nevermind, it is working with Robusta, Pager Duty is able to parse the values just fine.

@oscarmparedes
Copy link
Author

N/A

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

No branches or pull requests

1 participant