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

Override send demo alert grouping behavior #3129

Open
mderynck opened this issue Oct 5, 2023 · 1 comment · May be fixed by #4261
Open

Override send demo alert grouping behavior #3129

mderynck opened this issue Oct 5, 2023 · 1 comment · May be fixed by #4261

Comments

@mderynck
Copy link
Contributor

mderynck commented Oct 5, 2023

What would you like to see!

Currently when you Send demo alert it ignores the grouping template. This behaviour is useful since often when sending a demo alert we are more interested in testing notifications and escalation chains so if the demo alert was grouped to an already existing group it would be confusing.

However in the case you actually want to test the grouping behaviour you are not able to do so through the web UI (it always generates a unique grouping). You can work around this by having the UI generate a curl command, if you use the curl command it will not override the grouping behaviour (which is confusing in a different way).

It would be nice if we exposed a consistent way to enable/disable grouping when sending demo alerts. Possibly this could be a specific key/value in the payload we document instead of the behaviour being fixed in code.

Product Area

Alert Flow & Configuration

Anything else to add?

No response

@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2023

The current version of Grafana OnCall, at the time this issue was opened, is v1.3.43. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!

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

Successfully merging a pull request may close this issue.

2 participants