From ff822f3f8317de21fd8ac876efd2087fe0fe681c Mon Sep 17 00:00:00 2001 From: Gwynne Monahan Date: Thu, 8 Aug 2024 14:50:18 -0500 Subject: [PATCH] OSSM-6920 [DOC] OTEL + Tempo Merge Review Clean up --- modules/ossm-configuring-distr-tracing-tempo.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/ossm-configuring-distr-tracing-tempo.adoc b/modules/ossm-configuring-distr-tracing-tempo.adoc index cbff7f4cf8..984bf6b785 100644 --- a/modules/ossm-configuring-distr-tracing-tempo.adoc +++ b/modules/ossm-configuring-distr-tracing-tempo.adoc @@ -15,9 +15,9 @@ You can create a {OTELName} instance in a mesh namespace and configure it to sen .Prerequisites -* You created a TempoStack instance using the Red Hat {TempoOperator} in the `tracing-system` namespace. For more information, see "Installing {TempoName}" in the "Additional resources" section. +* You created a TempoStack instance using the Red Hat {TempoOperator} in the `tracing-system` namespace. For more information, see "Installing {TempoName}". -* You installed the {OTELOperator} in either the recommended namespace or the `openshift-operators` namespace. For more information, see "Installing the {OTELName}" in the "Additional resources" section. +* You installed the {OTELOperator} in either the recommended namespace or the `openshift-operators` namespace. For more information, see "Installing the {OTELName}". * If using {SMProductName} 2.5 or earlier, set the `spec.tracing.type` parameter of the `ServiceMeshControlPlane` resource to `None` so tracing data can be sent to the OpenTelemetry Collector. @@ -64,7 +64,7 @@ spec: You only need to create one instance of the OpenTelemetry Collector in one of the `ServiceMeshMemberRoll` member namespaces. ==== -. Check the `otel-collector` pod log and verify that the pod is running. +. Check the `otel-collector` pod log and verify that the pod is running: + .Example `otel-collector` pod log check [source,terminal]