[Andreas] I propose to restructure our OpenTelemetry docs into the following main sections:

Instrumenting Applications

• configure instrumentation and auto-instrumentation, sidecar injection

Receiving Telemetry Data

• receive metrics (instructions how to scrape the federate endpoint) / remote-write https://issues.redhat.com/browse/TRACING-5561 
• receive platform metrics
• receive workload metrics
• receive logs (instructions how to setup filelog receiver)
• see https://github.com/openshift/openshift-docs/pull/102189

Forwarding Telemetry Data

• forward to dynatrace (TODO)
• forward to Google (TODO)
• to 3rd party system which supports OTLP https://issues.redhat.com/browse/TRACING-5358 

Storing Telemetry Data

• store metrics in user-workload monitoring stack
• store logs in LokiStack
• store traces in TempoStack

 [Pavol] I would propose following changes:

• About Red Hat build of OpenTelemetry - Understanding the OpenTelemetry Collector architecture and features
  To
  • About Red Hat build of OpenTelemetry - Understanding the OpenTelemetry architecture and features

• I would suggest renaming the chapter "Receiving telemetry data" to "Multi-cluster configuration". That chapter only talk about multi-cluster setup.
• I would suggest moving the chapter "Configuring the Collector metrics" to the troubleshooting section and renaming it to "Configuring internal Collector metrics"

      source: https://issues.redhat.com/browse/OBSDOCS-2703?focusedId=28836507&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28836507