HDDS-13680. migrate tracing to opentelemetry

[sumitagrawl]

What changes were proposed in this pull request?

Ozone is currently using OpenTracing with Jaegaer as the destination. Now the OpenTracing project is deprecated and no longer supported.

As part of this PR scope, its just migrating to OpenTelemetry interface with existing behavior and should able to work work with Jaeger.

Few changes:
env variable:

• OTEL_EXPORTER_OTLP_ENDPOINT: to specify endpoint with OTLP receiver, default: http://localhost:4317
• OTEL_TRACES_SAMPLER_ARG: sampler arg for sampling, with default 1.0 means every trace to be reported.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-13680

Parent JIRA:
https://issues.apache.org/jira/browse/HDDS-13679

How was this patch tested?

• Test with Jaegar UI using docker
• Existing test cases

Sample Output from Jaegar:

[adoroszlai]

Thanks @sumitagrawl for working on this.

[jojochuang]

From a quick look it looks good. Thanks @sumitagrawl Just a trivial text suggestion.

Client applications such as HBase support OpenTelemetry. I wonder if the traces started from HBase can connect correctly to the underlying Ozone traces. I couldn't get it working when Ozone was using OpenTracing.

[sumitagrawl]

From a quick look it looks good. Thanks @sumitagrawl Just a trivial text suggestion.

Client applications such as HBase support OpenTelemetry. I wonder if the traces started from HBase can connect correctly to the underlying Ozone traces. I couldn't get it working when Ozone was using OpenTracing.

Yes, it will able to trace. Few improvement JIRA to be raised for details, I have prepared design doc for the same,
#9051