jlengrand/bugsink
1
0
Fork 0
mirror of https://github.com/jlengrand/bugsink.git synced 2026-03-10 08:01:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

minor textual changes in DESIGN doc

Browse Source
This commit is contained in:
Klaas van Schelven
2024-03-08 19:46:28 +01:00
parent fd1f54044b
commit 15e9d8042c
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
DESIGN-alerts.md
View File

@@ -37,7 +37,7 @@ symmetry/tracability between what's going on in the UI and the alerts that are g
## "Later": more than first-time-only
(The below only works if you let go of the idea that auto-mute is the only way you get volume-based alerts).
(The below only works if you let go of the idea that the only way you get volume-based alerts is when some unmute-condition occurs).
Rather than just having first-time only rules, you could have alerting rules that are triggered when a condition
persists. e.g.
@@ -70,7 +70,8 @@ alerting has (for now) been chosen not to implement in favor of vbc-unmute-rules
## Chat-Ops
You may configure any number of chat-ops endpoints (mattermost/slack channels). These are not connected to individual
users. There's likely a default setting at the organization level.
users. There's likely a default setting at the organization level. But it's also well imaginable that some project-based
settings are necessary, e.g. when each project has its own channel.
The chat-ops channels always receive the per-project configured set of notifications, i.e. the threshold cannot be
changed per chat-op-channel (as with users).