sravani-revuri opened a new pull request, #10077:
URL: https://github.com/apache/ozone/pull/10077
## What changes were proposed in this pull request?
The Ozone client needs the flexibility to either initiate a new span or
continue an existing application-level trace by creating a child span.
Currently, if ozone.tracing.enabled is false, all tracing is suppressed. A
specific scenario arises when the Ozone client should only trace if it's
explicitly enabled to continue an application's existing trace.
* **When `ozone.tracing.enabled` is True:**
* The client uses the standard Ozone-initialized tracer (existing
behavior).
* **When `ozone.tracing.enabled` is False:**
* **If `application-aware` is True and an active span exists:** The
client will create child spans using the application’s `GlobalOpenTelemetry`
context. This allows Ozone operations to appear as children of the
application's spans.
* **If no active span exists:** No spans are created (standalone tracing
remains off).
* **If `application-aware` is False:** No spans are created regardless
of the application context.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-13803
## How was this patch tested?
Written unit tests and existing tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]