Proposed title of this feature request

OpenTelemetry collector troubleshooting docs

What is the nature and description of the request?

Users of the Red Hat build of OpenTelemetry can find it difficult to troubleshoot its configuration: all the way from signal generation till final visualization in the OpenShift or other consoles.

Upon completion of this Feature ticket, users need to have a clear guide to walk them through the troubleshooting process that leads them to understand which ends of a broken pipeline should be connected. In particular, troubleshooting guides need to exist for the pipelines:

• Logs
• Metrics
• Traces
• Connectors between pipelines

And shall provide a guide on how to check:

• Is my signal reaching the collector?
• Is my signal exported from the collector?
• Is my signal reaching the backend?
• Is my signal stored in the backend?

Why does the customer need this? (List the business requirements)

In order to easily configure the product and increase adoption.

List any affected packages or components.

OpenTelemetry collector

Instrumentation CR

Tempo

Console

Additional notes

Consider creating an epic per signal if it makes sense