centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'main' into dev

Browse source
This commit is contained in:
Matias Bordese 2023-11-09 10:22:24 -03:00
commit dd348f01f9
2 changed files with 12 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docs/sources/escalation-chains-and-routes/_index.md
View file

@ -56,9 +56,8 @@ need a larger time interval, use multiple wait steps in a row.
from an on-call schedule.
* `Resolve incident automatically` - resolve the alert group right now with status
`Resolved automatically`.
* `Notify whole slack channel` - send a notification to a slack channel (not recommended
to use as it will spam the channel).
* `Notify Slack User Group` - send a notification to a slack user group.
* `Notify whole slack channel` - send a notification to the users in the slack channel.
* `Notify Slack User Group` - send a notification to each member of a slack user group.
* `Trigger outgoing webhook` - trigger an [outgoing webhook][outgoing-webhooks].
* `Notify users one by one (round robin)` - each notification will be sent to a group of
users one by one, in sequential order in [round robin fashion](https://en.wikipedia.org/wiki/Round-robin_item_allocation).
@ -69,6 +68,14 @@ Useful when you want to get escalation only during working hours
passes some threshold
* `Repeat escalation from beginning (5 times max)` - loop the escalation chain
> **Note:** Both "**Notify whole Slack channel**" and "**Notify Slack User Group**" will filter OnCall registered users
matching the users in the Slack channel or Slack User Group with their profiles linked to their Slack accounts (ie. users
should have linked their Slack and OnCall users). In both cases, the filtered users satisfying the criteria above are
notified following their respective notification policies. However, to avoid **spamming** the Slack channel/thread,
users **won't be notified** in the alert group Slack **thread** (this is how the feature is currently implemented)
but instead notify them using their **other defined** options in
their [respective policies]([url](https://grafana.com/docs/oncall/latest/notify/#configure-user-notification-policies)).
### Notification types
Each escalation step that notifies a user, does so by triggering their personal notification steps. These are configured in the Grafana

4
helm/oncall/Chart.yaml
View file

@ -2,8 +2,8 @@ apiVersion: v2
name: oncall
description: Developer-friendly incident response with brilliant Slack integration
type: application
version: 1.3.50
appVersion: v1.3.50
version: 1.3.55
appVersion: v1.3.55
dependencies:
- name: cert-manager
version: v1.8.0