Repository: openshift/openshift-docs
Pull request #93526: OBSDOCS-1629: Fix
Author: login: max-cx
Labels: name: peer-review-done
description: Signifies that the peer review team has reviewed this PR
name: size/M
description: Denotes a PR that changes 30-99 lines, ignoring generated files.
name: merge-review-in-progress
description: Signifies that the merge review team is reviewing this PR
name: merge-review-needed
description: Signifies that the merge review team needs to review this PR
name: jira/valid-reference
description: Indicates that this PR references a valid Jira ticket of any type.
Created: 2025-05-19T08:55:38Z | Merged: 2025-05-29T20:41:08Z

<!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->

<!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
If a book is being created or modified, there are changes on the Customer Portal that must also be made.

* For more details about the information requested in this template, see:
  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->

Version(s): `main`, `4.19`
<!--- Specify the version or versions of OpenShift your PR applies to. -->

Issue: https://issues.redhat.com/browse/OBSDOCS-1629
<!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->

Link to docs preview:
<!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
- https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn
- https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn

QE review: N/A

Additional information: Fix for https://github.com/openshift/openshift-docs/pull/92944
<!--- Optional: Include additional context or expand the description here.--->

<!--- After you open your PR, ask for review from the OpenShift docs team:
  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->



Diff:
diff --git a/_attributes/common-attributes.adoc b/_attributes/common-attributes.adoc
index 653825843c64..25c4ee364553 100644
--- a/_attributes/common-attributes.adoc
+++ b/_attributes/common-attributes.adoc
@@ -128,19 +128,19 @@ endif::[]
 :ove-first: Red{nbsp}Hat OpenShift Virtualization Engine
 :ove: OpenShift Virtualization Engine
 //distributed tracing
-:DTProductName: Red{nbsp}Hat OpenShift Distributed Tracing Platform
+:DTProductName: Red Hat OpenShift Distributed Tracing Platform
 :DTShortName: Distributed Tracing Platform
 :DTProductVersion: 3.1
-:JaegerName: Red{nbsp}Hat OpenShift Distributed Tracing Platform (Jaeger)
-:JaegerOperator: Red{nbsp}Hat OpenShift Distributed Tracing Platform
+:JaegerName: Red Hat OpenShift Distributed Tracing Platform (Jaeger)
+:JaegerOperator: Red Hat OpenShift Distributed Tracing Platform
 :JaegerShortName: Distributed Tracing Platform (Jaeger)
-:JaegerOperator: Red{nbsp}Hat OpenShift Distributed Tracing Platform
+:JaegerOperator: Red Hat OpenShift Distributed Tracing Platform
 :JaegerVersion: 1.53.0
 :OTELName: Red{nbsp}Hat build of OpenTelemetry
 :OTELShortName: Red{nbsp}Hat build of OpenTelemetry
 :OTELOperator: Red{nbsp}Hat build of OpenTelemetry Operator
 :OTELVersion: 0.93.0
-:TempoName: Red{nbsp}Hat OpenShift Distributed Tracing Platform
+:TempoName: Red Hat OpenShift Distributed Tracing Platform
 :TempoShortName: Distributed Tracing Platform
 :TempoOperator: Tempo Operator
 :TempoVersion: 2.3.1
diff --git a/modules/distr-tracing-removing-instance-cli.adoc b/modules/distr-tracing-removing-instance-cli.adoc
index 0b0621e8f218..a6e622642ccb 100644
--- a/modules/distr-tracing-removing-instance-cli.adoc
+++ b/modules/distr-tracing-removing-instance-cli.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * observability/distr_tracing/distr_tracing_jaeger/dist-tracing-removing.adoc
+// * observability/distr_tracing/distr_tracing_jaeger/distr-tracing-removing.adoc
 
 [id="distr-tracing-removing-instance-cli_{context}"]
 = Removing a {JaegerShortName} instance by using the CLI
diff --git a/modules/distr-tracing-removing-instance.adoc b/modules/distr-tracing-removing-instance.adoc
index 488279b056ad..a93f0f419b72 100644
--- a/modules/distr-tracing-removing-instance.adoc
+++ b/modules/distr-tracing-removing-instance.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * observability/distr_tracing/distr_tracing_jaeger/dist-tracing-removing.adoc
+// * observability/distr_tracing/distr_tracing_jaeger/distr-tracing-removing.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="distr-tracing-removing-instance_{context}"]
diff --git a/modules/distr-tracing-sidecar-automatic.adoc b/modules/distr-tracing-sidecar-automatic.adoc
index 2a2d4ec782c7..7fc12c0ef396 100644
--- a/modules/distr-tracing-sidecar-automatic.adoc
+++ b/modules/distr-tracing-sidecar-automatic.adoc
@@ -3,7 +3,7 @@
 // * observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-configuring.adoc
 
 :_mod-docs-content-type: REFERENCE
-[id="dist-tracing-sidecar-automatic_{context}"]
+[id="distr-tracing-sidecar-automatic_{context}"]
 = Automatically injecting sidecars
 
 The {JaegerName} Operator can inject Jaeger Agent sidecars into deployment workloads. To enable automatic injection of sidecars, add the `sidecar.jaegertracing.io/inject` annotation set to either the string `true` or to the {JaegerShortName} instance name that is returned by running `$ oc get jaegers`.
diff --git a/modules/distr-tracing-tempo-remove-cli.adoc b/modules/distr-tracing-tempo-remove-cli.adoc
index 09aee02a8946..4c415125e090 100644
--- a/modules/distr-tracing-tempo-remove-cli.adoc
+++ b/modules/distr-tracing-tempo-remove-cli.adoc
@@ -1,6 +1,6 @@
 //Module included in the following assemblies:
 //
-//* observability/distr_tracing/dist-tracing-tempo-removing.adoc
+//* observability/distr_tracing/distr-tracing-tempo-removing.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="distr-tracing-removing-tempo-instance-cli_{context}"]
diff --git a/modules/distr-tracing-tempo-remove-web-console.adoc b/modules/distr-tracing-tempo-remove-web-console.adoc
index 4dd7b972bd16..fc9058a8ddc3 100644
--- a/modules/distr-tracing-tempo-remove-web-console.adoc
+++ b/modules/distr-tracing-tempo-remove-web-console.adoc
@@ -1,6 +1,6 @@
 //Module included in the following assemblies:
 //
-//* observability/distr_tracing/dist-tracing-tempo-removing.adoc
+//* observability/distr_tracing/distr-tracing-tempo-removing.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="distr-tracing-removing-tempo-instance_{context}"]
diff --git a/observability/distr_tracing/distr-tracing-architecture.adoc b/observability/distr_tracing/distr-tracing-architecture.adoc
index 64f731ebdfef..61f1df297e3e 100644
--- a/observability/distr_tracing/distr-tracing-architecture.adoc
+++ b/observability/distr_tracing/distr-tracing-architecture.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-architecture"]
 = About the {DTShortName}
-include::_attributes/common-attributes.adoc[]
 :context: distributed-tracing-architecture
 
 toc::[]
@@ -28,4 +28,4 @@ include::modules/distr-tracing-architecture.adoc[leveloffset=+1]
 == Additional resources
 
 // xreffing to the installation page until further notice because OTEL content is currently planned for internal restructuring across pages that is likely to result in renamed page files
-* xref:../otel/otel-installing.adoc#install-otel[{OTELName}]
+* xref:../../observability/otel/otel-installing.adoc#install-otel[{OTELName}]
diff --git a/observability/distr_tracing/distr-tracing-rn.adoc b/observability/distr_tracing/distr-tracing-rn.adoc
index cbac293cd1f0..3152576e182b 100644
--- a/observability/distr_tracing/distr-tracing-rn.adoc
+++ b/observability/distr_tracing/distr-tracing-rn.adoc
@@ -299,7 +299,7 @@ endif::openshift-rosa[]
 [id="distr-tracing_3-3-1_{context}"]
 == Release notes for {DTProductName} 3.3.1
 
-The {DTProductName} 3.3.1 is a maintenance release with no changes because the {DTProductName} is bundled with the {OTELName} that is xref:../otel/otel-rn.adoc#otel_rn[released] with a bug fix.
+The {DTProductName} 3.3.1 is a maintenance release with no changes because the {DTProductName} is bundled with the {OTELName} that is xref:../../observability/otel/otel-rn.adoc#otel_rn[released] with a bug fix.
 
 This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
 
@@ -393,7 +393,7 @@ The {JaegerName} 3.3.1 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
 In the {DTProductName} 3.3.1, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
 Red{nbsp}Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
 
-The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
+The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../../observability/otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:../../observability/distr_tracing/distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../../observability/otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
 
 ////
 [id="distr-tracing_3-3-1_jaeger-release-notes_removal-notice_{context}"]
@@ -522,7 +522,7 @@ The {JaegerName} 3.3 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
 In the {DTProductName} 3.3, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
 Red{nbsp}Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
 
-The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
+The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../../observability/otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:../../observability/distr_tracing/distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../../observability/otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
 
 ////
 [id="distr-tracing_3-3_jaeger-release-notes_removal-notice_{context}"]
diff --git a/observability/distr_tracing/distr-tracing-tempo-configuring.adoc b/observability/distr_tracing/distr-tracing-tempo-configuring.adoc
index 6bdb1cff3a9d..0435f14ce0c9 100644
--- a/observability/distr_tracing/distr-tracing-tempo-configuring.adoc
+++ b/observability/distr_tracing/distr-tracing-tempo-configuring.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-tempo-configuring"]
 = Configuring the {DTShortName}
-include::_attributes/common-attributes.adoc[]
 :context: distr-tracing-tempo-configuring
 
 toc::[]
diff --git a/observability/distr_tracing/distr-tracing-tempo-installing.adoc b/observability/distr_tracing/distr-tracing-tempo-installing.adoc
index 9c387a08e01c..6d82a2c3610b 100644
--- a/observability/distr_tracing/distr-tracing-tempo-installing.adoc
+++ b/observability/distr_tracing/distr-tracing-tempo-installing.adoc
@@ -1,14 +1,14 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-tempo-installing"]
 = Installing the {DTShortName}
-include::_attributes/common-attributes.adoc[]
 :context: distr-tracing-tempo-installing
 
 toc::[]
 
 [TIP]
 ====
-For information about installing the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc#dist-tracing-jaeger-installing[Installing] in the {JaegerShortName} documentation.
+For information about installing the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc#distr-tracing-jaeger-installing[Installing] in the {JaegerShortName} documentation.
 ====
 
 Installing the {TempoShortName} involves the following steps:
diff --git a/observability/distr_tracing/distr-tracing-tempo-removing.adoc b/observability/distr_tracing/distr-tracing-tempo-removing.adoc
index 92b082203833..791b0328254e 100644
--- a/observability/distr_tracing/distr-tracing-tempo-removing.adoc
+++ b/observability/distr_tracing/distr-tracing-tempo-removing.adoc
@@ -1,14 +1,14 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-tempo-removing"]
 = Removing the {DTShortName}
-include::_attributes/common-attributes.adoc[]
 :context: distr-tracing-tempo-removing
 
 toc::[]
 
 [TIP]
 ====
-For information about removing the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc#dist-tracing-jaeger-removing[Removing] in the {JaegerShortName} documentation.
+For information about removing the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc#distr-tracing-jaeger-removing[Removing] in the {JaegerShortName} documentation.
 ====
 
 The steps for removing the {TempoName} from an {product-title} cluster are as follows:
diff --git a/observability/distr_tracing/distr-tracing-tempo-troubleshooting.adoc b/observability/distr_tracing/distr-tracing-tempo-troubleshooting.adoc
index c39b327057a5..5987fe175d5c 100644
--- a/observability/distr_tracing/distr-tracing-tempo-troubleshooting.adoc
+++ b/observability/distr_tracing/distr-tracing-tempo-troubleshooting.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-tempo-troubleshooting"]
 = Troubleshooting the {DTShortName}
-include::_attributes/common-attributes.adoc[]
 :context: distr-tracing-tempo-troubleshooting
 
 toc::[]
diff --git a/observability/distr_tracing/distr-tracing-tempo-updating.adoc b/observability/distr_tracing/distr-tracing-tempo-updating.adoc
index bb5bb9433c61..a43a196b8e11 100644
--- a/observability/distr_tracing/distr-tracing-tempo-updating.adoc
+++ b/observability/distr_tracing/distr-tracing-tempo-updating.adoc
@@ -1,14 +1,14 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="distr-tracing-tempo-updating"]
 = Upgrading
-include::_attributes/common-attributes.adoc[]
 :context: distr-tracing-tempo-updating
 
 toc::[]
 
 [TIP]
 ====
-For information about upgrading the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc#dist-tracing-jaeger-updating[Upgrading] in the {JaegerShortName} documentation.
+For information about upgrading the deprecated {JaegerShortName}, see xref:../../observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc#distr-tracing-jaeger-updating[Upgrading] in the {JaegerShortName} documentation.
 ====
 
 For version upgrades, the {TempoOperator} uses the Operator Lifecycle Manager (OLM), which controls installation, upgrade, and role-based access control (RBAC) of Operators in a cluster.
diff --git a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc
index b9ae937d3158..d19c8c289213 100644
--- a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc
+++ b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-installing.adoc
@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="dist-tracing-jaeger-installing"]
+[id="distr-tracing-jaeger-installing"]
 = Installing the {JaegerShortName}
 include::_attributes/common-attributes.adoc[]
-:context: dist-tracing-jaeger-installing
+:context: distr-tracing-jaeger-installing
 
 toc::[]
 
diff --git a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc
index 8199cbf68037..5dea8e0f6c87 100644
--- a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc
+++ b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-removing.adoc
@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="dist-tracing-jaeger-removing"]
+[id="distr-tracing-jaeger-removing"]
 = Removing the {JaegerShortName}
 include::_attributes/common-attributes.adoc[]
-:context: dist-tracing-jaeger-removing
+:context: distr-tracing-jaeger-removing
 
 toc::[]
 
diff --git a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc
index 12d652d35562..8a95368acb38 100644
--- a/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc
+++ b/observability/distr_tracing/distr_tracing_jaeger/distr-tracing-jaeger-updating.adoc
@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="dist-tracing-jaeger-updating"]
+[id="distr-tracing-jaeger-updating"]
 = Upgrading the {JaegerShortName}
 include::_attributes/common-attributes.adoc[]
-:context: dist-tracing-jaeger-updating
+:context: distr-tracing-jaeger-updating
 
 toc::[]
 
diff --git a/observability/otel/otel-collector/otel-collector-configuration-intro.adoc b/observability/otel/otel-collector/otel-collector-configuration-intro.adoc
index 468c0b301467..ee280a5ff4a9 100644
--- a/observability/otel/otel-collector/otel-collector-configuration-intro.adoc
+++ b/observability/otel/otel-collector/otel-collector-configuration-intro.adoc
@@ -9,4 +9,5 @@ toc::[]
 The {OTELName} Operator uses a custom resource definition (CRD) file that defines the architecture and configuration settings to be used when creating and deploying the {OTELShortName} resources. You can install the default configuration or modify the file.
 
 include::modules/otel-collector-config-options.adoc[leveloffset=+1]
+
 include::modules/otel-creating-required-RBAC-resources-automatically.adoc[leveloffset=+1]
diff --git a/observability/otel/otel-config-multicluster.adoc b/observability/otel/otel-config-multicluster.adoc
index 7f56183aff45..58bcfcad6933 100644
--- a/observability/otel/otel-config-multicluster.adoc
+++ b/observability/otel/otel-config-multicluster.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-gathering-observability-data-from-multiple-clusters"]
 = Gathering the observability data from multiple clusters
-include::_attributes/common-attributes.adoc[]
 :context: otel-gathering-observability-data-from-multiple-clusters
 
 For a multicluster configuration, you can create one OpenTelemetry Collector instance in each one of the remote clusters and then forward all the telemetry data to one OpenTelemetry Collector instance.
diff --git a/observability/otel/otel-configuration-of-instrumentation.adoc b/observability/otel/otel-configuration-of-instrumentation.adoc
index a534d46cc578..7db773120b32 100644
--- a/observability/otel/otel-configuration-of-instrumentation.adoc
+++ b/observability/otel/otel-configuration-of-instrumentation.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-configuration-of-instrumentation"]
 = Configuring the instrumentation
-include::_attributes/common-attributes.adoc[]
 :context: otel-configuration-of-instrumentation
 
 toc::[]
@@ -10,4 +10,5 @@ toc::[]
 The {OTELName} Operator uses an `Instrumentation` custom resource that defines the configuration of the instrumentation.
 
 include::modules/otel-autoinstrumentation.adoc[leveloffset=+1]
+
 include::modules/otel-config-instrumentation.adoc[leveloffset=+1]
diff --git a/observability/otel/otel-configuring-metrics-for-monitoring-stack.adoc b/observability/otel/otel-configuring-metrics-for-monitoring-stack.adoc
index 9fe947cd7df9..282b225fca44 100644
--- a/observability/otel/otel-configuring-metrics-for-monitoring-stack.adoc
+++ b/observability/otel/otel-configuring-metrics-for-monitoring-stack.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-configuring-metrics-for-monitoring-stack"]
 = Configuring metrics for the monitoring stack
-include::_attributes/common-attributes.adoc[]
 :context: otel-configuring-metrics-for-monitoring-stack
 
 toc::[]
@@ -13,6 +13,7 @@ As a cluster administrator, you can configure the OpenTelemetry Collector custom
 * Configure the Prometheus receiver to scrape metrics from the in-cluster monitoring stack.
 
 include::modules/otel-config-send-metrics-monitoring-stack.adoc[leveloffset=+1]
+
 include::modules/otel-config-receive-metrics-monitoring-stack.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
diff --git a/observability/otel/otel-configuring-otelcol-metrics.adoc b/observability/otel/otel-configuring-otelcol-metrics.adoc
index 261aab7dc41a..230628bbd08e 100644
--- a/observability/otel/otel-configuring-otelcol-metrics.adoc
+++ b/observability/otel/otel-configuring-otelcol-metrics.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-configuring-metrics"]
 = Configuring the OpenTelemetry Collector metrics
-include::_attributes/common-attributes.adoc[]
 :context: otel-configuring-metrics
 
 The following list shows some of these metrics:
diff --git a/observability/otel/otel-forwarding-telemetry-data.adoc b/observability/otel/otel-forwarding-telemetry-data.adoc
index 7dfa6219fa13..ae352df2929d 100644
--- a/observability/otel/otel-forwarding-telemetry-data.adoc
+++ b/observability/otel/otel-forwarding-telemetry-data.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-forwarding-telemetry-data"]
 = Forwarding telemetry data
-include::_attributes/common-attributes.adoc[]
 :context: otel-forwarding-telemetry-data
 
 toc::[]
@@ -9,6 +9,7 @@ toc::[]
 You can use the OpenTelemetry Collector to forward your telemetry data.
 
 include::modules/otel-forwarding-traces.adoc[leveloffset=+1]
+
 include::modules/otel-forwarding-logs-to-tempostack.adoc[leveloffset=+1]
 
 ////
diff --git a/observability/otel/otel-installing.adoc b/observability/otel/otel-installing.adoc
index 71d67bf540a1..032a92d849ed 100644
--- a/observability/otel/otel-installing.adoc
+++ b/observability/otel/otel-installing.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="install-otel"]
 = Installing
-include::_attributes/common-attributes.adoc[]
 :context: install-otel
 
 toc::[]
diff --git a/observability/otel/otel-migrating.adoc b/observability/otel/otel-migrating.adoc
index 3b4f382db8dd..1e280c8c627f 100644
--- a/observability/otel/otel-migrating.adoc
+++ b/observability/otel/otel-migrating.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-migrating"]
 = Migrating
-include::_attributes/common-attributes.adoc[]
 :context: otel-migrating
 
 toc::[]
diff --git a/observability/otel/otel-removing.adoc b/observability/otel/otel-removing.adoc
index a4ddefdffef2..3c800179cc45 100644
--- a/observability/otel/otel-removing.adoc
+++ b/observability/otel/otel-removing.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-removing"]
 = Removing
-include::_attributes/common-attributes.adoc[]
 :context: otel-removing
 
 toc::[]
diff --git a/observability/otel/otel-sending-traces-and-metrics-to-otel-collector.adoc b/observability/otel/otel-sending-traces-and-metrics-to-otel-collector.adoc
index 58fc8cb9828b..0c5f738d80e0 100644
--- a/observability/otel/otel-sending-traces-and-metrics-to-otel-collector.adoc
+++ b/observability/otel/otel-sending-traces-and-metrics-to-otel-collector.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-sending-traces-and-metrics-to-otel-collector"]
 = Sending traces and metrics to the OpenTelemetry Collector
-include::_attributes/common-attributes.adoc[]
 :context: otel-sending-traces-and-metrics-to-otel-collector
 
 toc::[]
diff --git a/observability/otel/otel-troubleshooting.adoc b/observability/otel/otel-troubleshooting.adoc
index c0998a5af474..5ca6bb5df761 100644
--- a/observability/otel/otel-troubleshooting.adoc
+++ b/observability/otel/otel-troubleshooting.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-troubleshoot"]
 = Troubleshooting
-include::_attributes/common-attributes.adoc[]
 :context: otel-troubleshoot
 
 toc::[]
@@ -9,9 +9,13 @@ toc::[]
 The OpenTelemetry Collector offers multiple ways to measure its health as well as investigate data ingestion issues.
 
 include::modules/otel-troubleshoot-collecting-diagnostic-data-from-command-line.adoc[leveloffset=+1]
+
 include::modules/otel-troubleshoot-collector-logs.adoc[leveloffset=+1]
+
 include::modules/otel-troubleshoot-metrics.adoc[leveloffset=+1]
+
 include::modules/otel-troubleshoot-debug-exporter-stdout.adoc[leveloffset=+1]
+
 include::modules/otel-troubleshoot-network-traffic.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
@@ -30,4 +34,5 @@ To troubleshoot the instrumentation, look for any of the following issues:
 * Issues with data generation by the instrumentation libraries
 
 include::modules/otel-troubleshooting-instrumentation-injection-into-your-workload.adoc[leveloffset=+2]
+
 include::modules/otel-troubleshooting-telemetry-data-generation-by-the-instrumentation-libraries.adoc[leveloffset=+2]
diff --git a/observability/otel/otel-updating.adoc b/observability/otel/otel-updating.adoc
index 3ba2b0a94962..f7eab2350dae 100644
--- a/observability/otel/otel-updating.adoc
+++ b/observability/otel/otel-updating.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="otel-updating"]
 = Upgrading
-include::_attributes/common-attributes.adoc[]
 :context: otel-updating
 
 toc::[]


Reviews:
user: login: ocpdocs-vale-bot
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-20T09:29:45Z
user: login: ocpdocs-vale-bot
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-20T09:29:46Z
user: login: GroceryBoyJr
body: LGTM
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-28T18:54:53Z

Review comments:
diff_hunk: @@ -393,7 +393,7 @@ The {JaegerName} 3.3.1 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
 In the {DTProductName} 3.3.1, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
 Red{nbsp}Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
 
-The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
+The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../../observability/otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:../../observability/distr_tracing/distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../../observability/otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
path: observability/distr_tracing/distr-tracing-rn.adoc
user: login: ocpdocs-vale-bot
body: 🤖 **[error] OpenShiftAsciiDoc.SuggestAttribute**: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception. 
created_at: 2025-05-20T09:29:45Z
author_association: COLLABORATOR
diff_hunk: @@ -522,7 +522,7 @@ The {JaegerName} 3.3 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
 In the {DTProductName} 3.3, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
 Red{nbsp}Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
 
-The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
+The {JaegerOperator} Operator (Jaeger) link:https://access.redhat.com/solutions/7083722[will be removed] from the `redhat-operators` catalog in a future release. Users must xref:../../observability/otel/otel-migrating.adoc#distr-tracing-otel-migrating[migrate] to the xref:../../observability/distr_tracing/distr-tracing-tempo-installing.adoc#distr-tracing-tempo-installing[{TempoOperator}] and the xref:../../observability/otel/otel-installing.adoc#install-otel[{OTELName}] for distributed tracing collection and storage.
path: observability/distr_tracing/distr-tracing-rn.adoc
user: login: ocpdocs-vale-bot
body: 🤖 **[error] OpenShiftAsciiDoc.SuggestAttribute**: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception. 
created_at: 2025-05-20T09:29:46Z
author_association: COLLABORATOR

PR comments:
user: login: openshift-ci-robot
created_at: 2025-05-19T08:55:42Z
body: @max-cx: This pull request references [OBSDOCS-1629](https://issues.redhat.com//browse/OBSDOCS-1629) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/93526):

><!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s):
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue:
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-05-19T08:56:54Z
body: @max-cx: This pull request references [OBSDOCS-1629](https://issues.redhat.com//browse/OBSDOCS-1629) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/93526):

><!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s): `main`, `4.19`
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue: https://issues.redhat.com/browse/OBSDOCS-1629
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review: N/A
>
>Additional information: Fix for https://github.com/openshift/openshift-docs/pull/92944
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: ocpdocs-previewbot
created_at: 2025-05-19T09:02:27Z
body: 🤖 Tue May 27 22:59:18 - Prow CI generated the docs preview:
https://93526--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: [artifacts/updated_preview_urls.txt](https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_openshift-docs/93526/pull-ci-openshift-openshift-docs-main-validate-asciidoc/1927497932580327424/artifacts/validate-asciidoc/openshift-docs-preview-comment-pages/artifacts/updated_preview_urls.txt)
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-05-19T10:10:27Z
body: @max-cx: This pull request references [OBSDOCS-1629](https://issues.redhat.com//browse/OBSDOCS-1629) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/93526):

><!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s): `main`, `4.19`
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue: https://issues.redhat.com/browse/OBSDOCS-1629
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>- https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn
>- https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn
>
>QE review: N/A
>
>Additional information: Fix for https://github.com/openshift/openshift-docs/pull/92944
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: max-cx
created_at: 2025-05-27T12:15:32Z
body: /label peer-review needed
author_association: CONTRIBUTOR
user: login: max-cx
created_at: 2025-05-27T22:53:03Z
body: /label peer-review-needed
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-05-27T23:03:05Z
body: @max-cx: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=93526). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:max-cx).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-05-28T14:42:15Z
body: @max-cx: Those labels are not set on the issue: `merge-review-needed`

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/93526#issuecomment-2916607156):

>/remove-label merge-review-needed


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: GroceryBoyJr
created_at: 2025-05-28T18:48:28Z
body: /remove-label merge-review-needed
/label peer-review-in-progress
/remove-label peer-review-needed
/assign GroceryBoyJr
author_association: CONTRIBUTOR
user: login: GroceryBoyJr
created_at: 2025-05-28T18:55:26Z
body: /label peer-review-done
/remove-label peer-review-in-progress
/unassign GroceryBoyJr

author_association: CONTRIBUTOR
user: login: GroceryBoyJr
created_at: 2025-05-28T18:56:18Z
body: @max-cx I had to remove the merge-review-needed, per our process, and didn't add it back in (per our process). I don't mean to cause inconvenience! Please, just add the label back in when you are ready.
author_association: CONTRIBUTOR
user: login: max-cx
created_at: 2025-05-29T18:01:29Z
body: /label merge-review-needed
author_association: CONTRIBUTOR
user: login: michaelryanpeter
created_at: 2025-05-29T19:23:13Z
body: /label merge-review-in-progress
author_association: CONTRIBUTOR
user: login: michaelryanpeter
created_at: 2025-05-29T20:40:24Z
body: LGTM

There has been some debate as to whether or not to have the include statement above the h1 for assemblies that don't need it ([Slack thread](https://redhat-internal.slack.com/archives/C85JYPHL3/p1714588248066459?thread_ts=1714588116.719949&cid=C85JYPHL3)). Currently, our guidelines state to use it when you need it (first assembly in a section if that assembly has an attribute). The rule remains in place due to a bug in the asciidoc VS code extension.

Since this is valid asciidoc, isn't customer-facing, and has limited impact, I don't think it is worth blocking a merge. I only mention it for context/awareness. I'm not sure if it is worth following up in another PR unless something breaks. Please double check after everything is published on d.r.c.
author_association: CONTRIBUTOR
user: login: michaelryanpeter
created_at: 2025-05-29T20:41:19Z
body: /cherrypick enterprise-4.19
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-05-29T20:42:08Z
body: @michaelryanpeter: new pull request created: #93963

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/93526#issuecomment-2920535790):

>/cherrypick enterprise-4.19


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE