support cluster label for external alert manager

robusta-dev · Dec 9, 2023 · 5e8fd77 · 5e8fd77
1 parent 81e6c3f
commit 5e8fd77
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/configuration/alertmanager-integration/coralogix_managed_prometheus.rst b/docs/configuration/alertmanager-integration/coralogix_managed_prometheus.rst
@@ -93,7 +93,7 @@ To configure it:
           "generatorURL": "$ALERT_URL",
           "annotations": {},
           "labels": {
-            "cluster_name": "MY_CLUSTER_NAME", # make sure to add your cluster name here for this webhook
+            "cluster_name": "MY_CLUSTER_NAME", # make sure to add your cluster name here for this webhook. Both "cluster" or "cluster_name" labels are also supported
             "alertname": "$ALERT_NAME",
             "alert_url": "$ALERT_URL"
             # Add any additional alert specific fields here

diff --git a/docs/configuration/alertmanager-integration/outofcluster-prometheus.rst b/docs/configuration/alertmanager-integration/outofcluster-prometheus.rst
@@ -11,7 +11,7 @@ Configure Push Integration
 A push integration lets your central Prometheus send alerts to Robusta, as if they were in the same cluster:
 
 1. Enable cloud-routing of alerts by setting ``disableCloudRouting: false`` in ``generated_values.yaml``.
-2. Verify that all alerts contain a label named ``cluster_name``, matching the :ref:`cluster_name defined in Robusta's configuration <Global Config>`. This is necessary to identify which robusta-runner should receive alerts.
+2. Verify that all alerts contain a label named ``cluster_name`` or ``cluster``, matching the :ref:`cluster_name defined in Robusta's configuration <Global Config>`. This is necessary to identify which robusta-runner should receive alerts.
 3. Edit the configuration for your centralized AlertManager:
 
 .. admonition:: alertmanager.yaml