-
Notifications
You must be signed in to change notification settings - Fork 299
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
update web UI, Slack, and Telegram to allow silencing an acknowledged alert group #1831
Conversation
even if alert group is acknowledged
Does this avoid the issue of re-entering firing state and notifying someone? Also should this be done across the board for Slack and other message backends in one PR? There is some conflict with docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool change, let's do the same for slack/other messengers
…:grafana/oncall into jorlando/show-alert-group-silence-button
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not related to this change, but fixing some grammatical things I came across
… alert group (#1831) # What this PR does https://www.loom.com/share/1a6ef0d00c3b46ca80c120579d512dcc ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated (N/A) - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required)
What this PR does
https://www.loom.com/share/1a6ef0d00c3b46ca80c120579d512dcc
Checklist
pr:no public docs
PR label added if not required)CHANGELOG.md
updated (orpr:no changelog
PR label added if not required)