sravani-revuri opened a new pull request, #10477: URL: https://github.com/apache/ozone/pull/10477
## 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. A specific scenario arises when the Ozone client should only trace if it's explicitly enabled to continue an application's existing trace. Typically, ozone.tracing.enabled is false, indicating that no tracing should occur by default. However, for Ozone clients, dynamically updating this configuration based on the application's implementation is often not feasible. To address this, the Ozone client will leverage the application's tracer to continue tracing as a child span. This specific behavior will be controlled by an additional flag: ozone.tracing.client.application-aware (default: true) When ozone.tracing.client.application-aware is true, the Ozone client will utilize tracers provided by the application context. This allows the Ozone client to trace even if the ozone.tracing.enabled configuration is false, provided the application has configured and enabled its own tracing. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-13803 ## How was this patch tested? written 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]
