From ac64c723bd7f3742bd30e8892e0f9a53adb3054f Mon Sep 17 00:00:00 2001 From: Leif Madsen Date: Tue, 3 Oct 2023 10:17:53 -0400 Subject: [PATCH] Creating an alert does not use curl (#500) The Creating a standard alert route in Alertmanager section no longer uses curl to verify the configuration was loaded, since it uses the prometheus pod and the wget command instance. Removes an extra procedure step that is no longer applicable. --- .../proc_creating-an-alert-route-in-alertmanager.adoc | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc-Service-Telemetry-Framework/modules/proc_creating-an-alert-route-in-alertmanager.adoc b/doc-Service-Telemetry-Framework/modules/proc_creating-an-alert-route-in-alertmanager.adoc index 17b00289..3efc0c52 100644 --- a/doc-Service-Telemetry-Framework/modules/proc_creating-an-alert-route-in-alertmanager.adoc +++ b/doc-Service-Telemetry-Framework/modules/proc_creating-an-alert-route-in-alertmanager.adoc @@ -113,15 +113,6 @@ $ oc exec -it prometheus-default-0 -c prometheus -- sh -c "wget --header \"Autho . Verify that the `configYAML` field contains the changes you expect. -. To clean up the environment, delete the `curl` pod: -+ -[source,bash] ----- -$ oc delete pod curl - -pod "curl" deleted ----- - .Additional resources * For more information about the {OpenShift} secret and the Prometheus operator, see https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/alerting.md[Prometheus user guide on alerting].