public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-04-30 10:13:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

(from rancher/rancher) #40358 Include instructions for manually updating AlertmanagerConfig after chart update (#569)

Browse Source 
* (from rancher/rancher) #40358 Include instructions for manually updating config after monitoring chart update

* applied suggestions from review

* Update versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/receivers.md
This commit is contained in:
Marty Hernandez Avedon
2023-04-27 17:34:08 -04:00
committed by GitHub
parent 8e532034bb
commit 4c332fa834
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/receivers.md
+12
View File
@@ -237,6 +237,18 @@ It is also possible to send alerts to multiple notification systems. One way is
You can also set up multiple receivers by using the `continue` option for a route, so that the alerts sent to a receiver continue being evaluated in the next level of the routing tree, which could contain another receiver.
## Configuring AlertmanagerConfig After A Chart Upgrade
If you have a cluster that uses SMS or Microsoft Teams alerts, and upgrade the Monitoring chart from 100.1.3+up19.0.3 to 100.2.0+up40.1.2, you may no longer receive alerts. This is due to a change to an upstream change to [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator/) that helps prevent naming collisions.
You must manually edit the configuration map to continue to receive alerts:
1. Click on **☰** and select the relevant cluster.
1. Select **More Resources** > **Core** > **ConfigMaps**.
1. Find the row corresponding to the ConfigMap for **Sachet** (for SMS alerts) or **prom2teams** (for Microsoft Teams alerts). Click the **⋮** and select **Edit YAML**.
1. Update the delimiters in the receiver's `name` field, replacing `-` characters with `/`, according to the following scheme: `<namespace>\<alertManagerConfig>\<receiverName>`. For example, if the receiver's name is `default-amc-test-prom2sms`, update it to `default/amc-test/prom2sms`.
1. Click **Save**.
1. Redeploy the workloads associated with Alertmanager and Sachet or prom2teams, to ensure that they receive the updated configuration.
## Example Alertmanager Configs