OBSDOCS-949-conditionalize-observability-overview

Author: bburt-rh

_topic_maps/_topic_map_osd.yml

@@ -1149,6 +1149,8 @@ Name: Observability
 Dir: observability
 Distros: openshift-dedicated
 Topics:
+- Name: Observability overview
+  File: index
 - Name: Monitoring
   Dir: monitoring
   Distros: openshift-dedicated

_topic_maps/_topic_map_rosa.yml

@@ -1403,6 +1403,8 @@ Name: Observability
 Dir: observability
 Distros: openshift-rosa
 Topics:
+- Name: Observability overview
+  File: index
 - Name: Monitoring
   Dir: monitoring
   Distros: openshift-rosa

observability/index.adoc

@@ -6,15 +6,23 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-
+ifndef::openshift-dedicated,openshift-rosa[]
 {ObservabilityLongName} provides real-time visibility, monitoring, and analysis of various system metrics, logs, traces, and events to help users quickly diagnose and troubleshoot issues before they impact systems or applications. To help ensure the reliability, performance, and security of your applications and infrastructure, {product-title} offers the following {ObservabilityShortName} components:
+endif::openshift-dedicated,openshift-rosa[]
+
+ifdef::openshift-dedicated,openshift-rosa[]
+{ObservabilityLongName} provides real-time visibility, monitoring, and analysis of various system metrics, logs, and events to help users quickly diagnose and troubleshoot issues before they impact systems or applications. To help ensure the reliability, performance, and security of your applications and infrastructure, {product-title} offers the following {ObservabilityShortName} components:
+endif::openshift-dedicated,openshift-rosa[]
 
 * Monitoring
-* {logging-uc} 
+* {logging-uc}
+ifndef::openshift-dedicated,openshift-rosa[]
 * Distributed tracing
 * {OTELName}
 * Network Observability
 * {PM-shortname-c}
+endif::openshift-dedicated,openshift-rosa[]
+
 
 {ObservabilityLongName} connects open-source observability tools and technologies to create a unified {ObservabilityShortName} solution. The components of {ObservabilityLongName} work together to help you collect, store, deliver, analyze, and visualize data.
 
@@ -24,28 +32,26 @@ Monitor the in-cluster health and performance of your applications running on {p
 
 Monitoring stack components are deployed by default in every {product-title} installation and are managed by the Cluster Monitoring Operator (CMO). These components include Prometheus, Alertmanager, Thanos Querier, and others. The CMO also deploys the Telemeter Client, which sends a subset of data from platform Prometheus instances to Red Hat to facilitate Remote Health Monitoring for clusters.
 
-For more information, see xref:../observability/monitoring/monitoring-overview.adoc#monitoring-overview[Monitoring overview] and xref:../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring]. 
+For more information, see xref:../observability/monitoring/monitoring-overview.adoc#monitoring-overview[Monitoring overview] and xref:../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring].
 
 [id="cluster-logging-index"]
-== Logging 
+== Logging
 Collect, visualize, forward, and store log data to troubleshoot issues, identify performance bottlenecks, and detect security threats. In logging 5.7 and later versions, users can configure the LokiStack deployment to produce customized alerts and recorded metrics.
 
 For more information, see xref:../observability/logging/cluster-logging.adoc#cluster-logging[About Logging].
-//after the file is added to the observability directory, update xref path to ../observability/logging/cluster-logging.adoc#cluster-logging[About Logging].
 
+ifdef::openshift-enterprise,openshift-origin[]
 [id="distr-tracing-architecture-index"]
 == Distributed tracing
 Store and visualize large volumes of requests passing through distributed systems, across the whole stack of microservices, and under heavy loads. Use it for monitoring distributed transactions, gathering insights into your instrumented services, network profiling, performance and latency optimization, root cause analysis, and troubleshooting the interaction between components in modern cloud-native microservices-based applications.
 
 For more information, see xref:distr_tracing/distr_tracing_arch/distr-tracing-architecture.adoc#distributed-tracing-architecture[Distributed tracing architecture].
-//after the file is added to the observability directory, update xref path to ../observability/distr_tracing/distr_tracing_arch/distr-tracing-architecture.adoc#distributed-tracing-architecture[Distributed tracing architecture].
 
 [id="otel-release-notes-index"]
 == {OTELName}
-Instrument, generate, collect, and export telemetry traces, metrics, and logs to analyze and understand your software's performance and behavior. Use open-source back ends like Tempo or Prometheus, or use commercial offerings. Learn a single set of APIs and conventions, and own the data that you generate. 
+Instrument, generate, collect, and export telemetry traces, metrics, and logs to analyze and understand your software's performance and behavior. Use open-source back ends like Tempo or Prometheus, or use commercial offerings. Learn a single set of APIs and conventions, and own the data that you generate.
 
 For more information, see xref:otel/otel-installing.adoc#install-otel[{OTELName}].
-//possibly outdated comment: after the file is added to the observability directory, update xref path to ../observability/otel/otel-release-notes.adoc#otel-release-notes[{OTELName} release notes].
 
 [id="network-observability-overview-index"]
 == Network Observability
@@ -54,7 +60,9 @@ Observe the network traffic for {product-title} clusters and create network flow
 For more information, see xref:../observability/network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability overview].
 
 [id="power-monitoring-overview-index"]
-== Power monitoring 
+== Power monitoring
 Monitor the power usage of workloads and identify the most power-consuming namespaces running in a cluster with key power consumption metrics, such as CPU or DRAM measured at the container level. Visualize energy-related system statistics with the {PM-operator}.
 
 For more information, see xref:../observability/power_monitoring/power-monitoring-overview.adoc#power-monitoring-overview[Power monitoring overview].
+endif::[]
+