OSSM3: Tracing output not present, despite Telemetry object being configured.

Solution Verified - Updated -

Issue

  • OSSM3 mesh members do not log traces within jaeger/tempo and/or kiali.
  • There is no trace information printed to standard out within the otel-collector pod logs even when debugging is configured.

Environment

  • Red Hat OpenShift Service Mesh 3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content