From b6194596e8c2b619a782db771664fb2b44ce2252 Mon Sep 17 00:00:00 2001 From: chelo Date: Sun, 11 Oct 2020 12:01:16 +0200 Subject: [PATCH] improve documentation alertmanager --- Documentation/user-guides/alerting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/user-guides/alerting.md b/Documentation/user-guides/alerting.md index b26a3d6db1..117a9c2d3c 100644 --- a/Documentation/user-guides/alerting.md +++ b/Documentation/user-guides/alerting.md @@ -52,7 +52,7 @@ receivers: Save the above Alertmanager config in a file called `alertmanager.yaml` and create a secret from it using `kubectl`. Alertmanager instances require the secret resource naming to follow the format -`alertmanager-{ALERTMANAGER_NAME}`. In the previous example, the name of the Alertmanager is `example`, so the secret name must be `alertmanager-example`, and the name of the config file `alertmanager.yaml` +`alertmanager-{ALERTMANAGER_NAME}`. In the previous example, the name of the Alertmanager is `example`, so the secret name must be `alertmanager-example`, and the name of the config file `alertmanager.yaml`. Also, the name of the secret can be set through the field `configSecret` in Alertmanager configuration, if you desire to use a different one. ```bash $ kubectl create secret generic alertmanager-example --from-file=alertmanager.yaml