-
Epic
-
Resolution: Done
-
Blocker
-
OSSM 2.5.0
-
None
-
Support Distributed Tracing 3
-
False
-
None
-
False
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
-
To Do
-
0% To Do, 9% In Progress, 91% Done
OpenShift Distributed Tracing 3(Based on Tempo) is set to GA shortly, and we will need to assert our support for it. The existing tracing infrastructure, based on Jaeger, will be deprecated and EOLed in the future.
Documentation of Tracing Platform (Tempo): https://docs.openshift.com/container-platform/4.14/distr_tracing/distr_tracing_tempo/distr-tracing-tempo-installing.html
Documentation of Tracing Collection (OTEL): https://docs.openshift.com/container-platform/4.14/distr_tracing/distr_tracing_otel/distr-tracing-otel-installing.html
This should include:
- Testing OSSM with Tempo and OTEL
- Documenting OSSM integration with Tempo and OTEL (if extra steps are required beyond deploying the Tracing Platform & Collection operators).
This does NOT include:
- Removing existing tracing documentation for Jaeger
- Deprecating OSSM's current Jaeger integration and Elasticsearch (via SMCP) - this should be evaluated though, potentially something to do in 2.6.
- is related to
-
OSSM-6269 Support Red Hat build of OpenTelemetry for Tracing
-
- In Progress
-
- relates to
-
OSSM-6015 Tempo known issue
-
- Closed
-
-
OSSM-6009 Request for fetch traces is timeouted after 30s even though I set a higher timeout in external_services.tracing.query_timeout
-
- Refinement
-
-
TRACING-3886 OSSM Tracing Tempo Stack in a SMMR member namespace. Cannot access queryFrontend.
-
- Backlog
-
-
OSSM-5995 OOMKilled in tempo-sample-query-frontend
-
- Closed
-
- mentioned on
