Merge pull request #90619 from openshift-cherrypick-robot/cherry-pick-90345-to-enterprise-4.19

[enterprise-4.19] OBSDOCS-1394: Issue in file observability/monitoring/accessing-third-…

modules/accessing-metrics-outside-cluster.adoc

@@ -34,7 +34,7 @@ $ TOKEN=$(oc whoami -t)
 +
 [source,terminal]
 ----
-$ HOST=$(oc -n openshift-monitoring get route thanos-querier -ojsonpath={.status.ingress[].host})
+$ HOST=$(oc -n openshift-monitoring get route thanos-querier -ojsonpath='{.status.ingress[].host}')
 ----
 
 . Set the namespace to the namespace in which your service is running by using the following command:

modules/monitoring-accessing-third-party-monitoring-web-service-apis.adoc

@@ -32,7 +32,7 @@ $ TOKEN=$(oc whoami -t)
 +
 [source,terminal]
 ----
-$ HOST=$(oc -n openshift-monitoring get route alertmanager-main -ojsonpath={.status.ingress[].host})
+$ HOST=$(oc -n openshift-monitoring get route alertmanager-main -ojsonpath='{.status.ingress[].host}')
 ----
 
 . Query the service API receivers for Alertmanager by running the following command:

modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc

@@ -75,7 +75,7 @@ endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 +
 [source,terminal]
 ----
-$ HOST=$(oc -n openshift-monitoring get route prometheus-k8s -ojsonpath={.status.ingress[].host})
+$ HOST=$(oc -n openshift-monitoring get route prometheus-k8s -ojsonpath='{.status.ingress[].host}')
 ----
 +
 .. Extract an authentication token by running the following command:

modules/monitoring-querying-metrics-by-using-the-federation-endpoint-for-prometheus.adoc

@@ -57,7 +57,7 @@ $ TOKEN=$(oc whoami -t)
 +
 [source,terminal]
 ----
-$ HOST=$(oc -n openshift-monitoring get route prometheus-k8s-federate -ojsonpath={.status.ingress[].host})
+$ HOST=$(oc -n openshift-monitoring get route prometheus-k8s-federate -ojsonpath='{.status.ingress[].host}')
 ----
 
 . Query metrics from the `/federate` route.