[
https://issues.apache.org/jira/browse/HDDS-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Agrawal updated HDDS-13679:
---------------------------------
Description:
Ozone is currently using OpenTracing with Jaegaer as the destination. Now the
OpenTracing project is deprecated and no longer supported. It is suggested to
Migrate *OpenTelemetry which is standard* and supports various tools including
Jaeger as UI to show traces.
Migration:
# Make use of OpenTelemetry methods
# Jaeger is supported with OTLP protocol over 4217 port with grpc
# change env variable naming to be used for tracing
# using standard *W3CTraceContextPropagator* for propogating context
Improvement:
* SpanKind addition as Server, Client, Internal, producer, consumer
* Service Name in trace to be more visual tracking like, OM-IP:Port,
SCM-IP:Port, OzoneClient-PID
* Tracing hierarchy to be validated for flows
* Dynamic enable trace log for OM/SCM/DN
* Trace documentation
New exploratory feature:
* Tracing hierarch to continue Span from User code (no need new trace start
from Ozone Client) for E2E tracing
* Tracing level control external tracing, internal tracing, include thread
tracing
was:
Ozone is currently using OpenTracing with Jaegaer as the destination. Now the
OpenTracing project is deprecated and no longer supported. It is suggested to
Migrate *OpenTelemetry which is standard* and supports various tools including
Jaeger as UI to show traces.
Migration:
# Make use of OpenTelemetry methods
# Jaeger is supported with OTLP protocol over 4217 port with grpc
# change env variable naming to be used for tracing
# using standard *W3CTraceContextPropagator* for propogating context
Improvement:
* SpanKind addition as Server, Client, Internal, producer, consumer
* Service Name in trace to be more visual tracking like, OM-IP:Port,
SCM-IP:Port, OzoneClient-PID
* Tracing hierarchy to be validated for flows
New exploratory feature:
* Tracing hierarch to continue Span from User code (no need new trace start
from Ozone Client) for E2E tracing
* Tracing level control external tracing, internal tracing, include thread
tracing
> Migrate Tracing to OpenTelemetry as OpenTracing is depreciated
> --------------------------------------------------------------
>
> Key: HDDS-13679
> URL: https://issues.apache.org/jira/browse/HDDS-13679
> Project: Apache Ozone
> Issue Type: Epic
> Reporter: Sumit Agrawal
> Priority: Major
>
> Ozone is currently using OpenTracing with Jaegaer as the destination. Now the
> OpenTracing project is deprecated and no longer supported. It is suggested to
> Migrate *OpenTelemetry which is standard* and supports various tools
> including Jaeger as UI to show traces.
>
> Migration:
> # Make use of OpenTelemetry methods
> # Jaeger is supported with OTLP protocol over 4217 port with grpc
> # change env variable naming to be used for tracing
> # using standard *W3CTraceContextPropagator* for propogating context
>
> Improvement:
> * SpanKind addition as Server, Client, Internal, producer, consumer
> * Service Name in trace to be more visual tracking like, OM-IP:Port,
> SCM-IP:Port, OzoneClient-PID
> * Tracing hierarchy to be validated for flows
> * Dynamic enable trace log for OM/SCM/DN
> * Trace documentation
> New exploratory feature:
> * Tracing hierarch to continue Span from User code (no need new trace start
> from Ozone Client) for E2E tracing
> * Tracing level control external tracing, internal tracing, include thread
> tracing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
