openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

OSSM-6920 [DOC] OTEL + Tempo Merge Review Clean up

Browse Source
This commit is contained in:
Gwynne Monahan
2024-08-08 14:50:18 -05:00
committed by openshift-cherrypick-robot
parent 99c59a5b72
commit ff822f3f83
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
modules/ossm-configuring-distr-tracing-tempo.adoc
View File

@@ -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]