HDDS-14765. Improve Trace Hierarchy for Ozone Shell Put Key Command

[sravani-revuri]

What changes were proposed in this pull request?

The tracing for the put key command is currently fragmented. Instead of one continuous trace with multiple spans, each function call opens a new trace as a separate root.

Proposed Changes
The goal is to ensure all actions belong to the same trace using a parent-child hierarchy.
Modify TracingUtil to check for an existing trace context before creating a new span:

• If a trace is already active, the new function call should join it as a span (child).
• If no trace is active, it should start the initial trace (parent).

What is the link to the Apache JIRA

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

How was this patch tested?

Tested with Jaeger UI using Docker.

[sravani-revuri]

@sumitagrawl , could you please review these changes.

[Gargi-jais11]

Thanks @sravani-revuri for the patch.
Please find inlined comments.

[Gargi-jais11]

@sravani-revuri Please add some tests in either TestTracingUtil or TestTraceAllMethod for checking.

1. Call a method annotated with @SkipTracing and assert no span is created.
2. Call a @SkipTracing method that throws and assert the exception is propagated unwrapped.
3. Use createProxy with an interface that has @SkipTracing methods and assert they run correctly without creating spans.

[yandrey321]

lgtm

[Gargi-jais11]

Thanks @sravani-revuri for updating the patch. Overall LGTM.

[adoroszlai]

@Gargi-jais11 please quote Java annotations (@SkipTracing) to avoid mentioning unrelated GitHub users

[Gargi-jais11]

@Gargi-jais11 please quote Java annotations (@SkipTracing) to avoid mentioning unrelated GitHub users

Thanks @adoroszlai, realised it just now when I checked it.