From 1a39b56ea3fed9f18ff31cbf802af0af6c309eea Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Thu, 2 Nov 2023 11:24:46 +0000 Subject: [PATCH 1/9] Release oncall Helm chart 1.3.51 --- helm/oncall/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml index ed4d6ec6..3b3ead5a 100644 --- a/helm/oncall/Chart.yaml +++ b/helm/oncall/Chart.yaml @@ -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.51 +appVersion: v1.3.51 dependencies: - name: cert-manager version: v1.8.0 From cbee2cfa2870013f1249cdef0928220f4ff8f6ff Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Thu, 2 Nov 2023 12:07:31 +0000 Subject: [PATCH 2/9] Release oncall Helm chart 1.3.52 --- helm/oncall/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml index 3b3ead5a..4e70f04f 100644 --- a/helm/oncall/Chart.yaml +++ b/helm/oncall/Chart.yaml @@ -2,8 +2,8 @@ apiVersion: v2 name: oncall description: Developer-friendly incident response with brilliant Slack integration type: application -version: 1.3.51 -appVersion: v1.3.51 +version: 1.3.52 +appVersion: v1.3.52 dependencies: - name: cert-manager version: v1.8.0 From 4449b0977e55698f346e6d9c48869d3f1fb10207 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Fri, 3 Nov 2023 18:11:47 +0000 Subject: [PATCH 3/9] Release oncall Helm chart 1.3.53 --- helm/oncall/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml index 4e70f04f..81e7e00b 100644 --- a/helm/oncall/Chart.yaml +++ b/helm/oncall/Chart.yaml @@ -2,8 +2,8 @@ apiVersion: v2 name: oncall description: Developer-friendly incident response with brilliant Slack integration type: application -version: 1.3.52 -appVersion: v1.3.52 +version: 1.3.53 +appVersion: v1.3.53 dependencies: - name: cert-manager version: v1.8.0 From 4702cf7370d13c24537bc287b93471771b67c286 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Mon, 6 Nov 2023 20:45:56 +0000 Subject: [PATCH 4/9] Release oncall Helm chart 1.3.54 --- helm/oncall/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml index 81e7e00b..c8c86ab3 100644 --- a/helm/oncall/Chart.yaml +++ b/helm/oncall/Chart.yaml @@ -2,8 +2,8 @@ apiVersion: v2 name: oncall description: Developer-friendly incident response with brilliant Slack integration type: application -version: 1.3.53 -appVersion: v1.3.53 +version: 1.3.54 +appVersion: v1.3.54 dependencies: - name: cert-manager version: v1.8.0 From 37861ac2306119a32641822f058eedd3da4c6305 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Tue, 7 Nov 2023 18:33:20 +0000 Subject: [PATCH 5/9] Release oncall Helm chart 1.3.55 --- helm/oncall/Chart.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/helm/oncall/Chart.yaml b/helm/oncall/Chart.yaml index c8c86ab3..12eb4b2d 100644 --- a/helm/oncall/Chart.yaml +++ b/helm/oncall/Chart.yaml @@ -2,8 +2,8 @@ apiVersion: v2 name: oncall description: Developer-friendly incident response with brilliant Slack integration type: application -version: 1.3.54 -appVersion: v1.3.54 +version: 1.3.55 +appVersion: v1.3.55 dependencies: - name: cert-manager version: v1.8.0 From 3683f407f492c161651cf27711f0f562d955e86c Mon Sep 17 00:00:00 2001 From: Pangidoan Butar <38452094+doanbutar@users.noreply.github.com> Date: Thu, 9 Nov 2023 09:28:32 +0800 Subject: [PATCH 6/9] A few clarifications and updates for "Notify whole Slack channel" and "Notify Slack User Group" https://github.com/grafana/support-escalations/issues/8169#issuecomment-1799997674 --- docs/sources/escalation-chains-and-routes/_index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md index 2c9a255f..a372cccf 100644 --- a/docs/sources/escalation-chains-and-routes/_index.md +++ b/docs/sources/escalation-chains-and-routes/_index.md @@ -69,6 +69,11 @@ 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 From 7945ad620c55d0312e81950191113bd96f093e35 Mon Sep 17 00:00:00 2001 From: Matias Bordese Date: Thu, 9 Nov 2023 09:34:01 -0300 Subject: [PATCH 7/9] Fix lint and extra minor update --- .../sources/escalation-chains-and-routes/_index.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md index a372cccf..b066c52c 100644 --- a/docs/sources/escalation-chains-and-routes/_index.md +++ b/docs/sources/escalation-chains-and-routes/_index.md @@ -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,9 +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. + > **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)). + > 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 From f46df97c6bc1bce0681e011f158d6a36df7074cb Mon Sep 17 00:00:00 2001 From: Matias Bordese Date: Thu, 9 Nov 2023 09:37:39 -0300 Subject: [PATCH 8/9] Fix lint issue --- docs/sources/escalation-chains-and-routes/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md index b066c52c..4ca8cd58 100644 --- a/docs/sources/escalation-chains-and-routes/_index.md +++ b/docs/sources/escalation-chains-and-routes/_index.md @@ -72,7 +72,7 @@ passes some threshold > 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)). From a1703c7fdb991caf9f9dd8739deccc1adee7ddd1 Mon Sep 17 00:00:00 2001 From: Matias Bordese Date: Thu, 9 Nov 2023 09:52:15 -0300 Subject: [PATCH 9/9] Really fix docs lint --- .../escalation-chains-and-routes/_index.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md index 4ca8cd58..036ea6d0 100644 --- a/docs/sources/escalation-chains-and-routes/_index.md +++ b/docs/sources/escalation-chains-and-routes/_index.md @@ -68,15 +68,13 @@ 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)). - +> **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