You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "dentiny (via GitHub)" <gi...@apache.org> on 2026/04/09 21:56:56 UTC

[I] new feature: end-to-end tracing capability [opendal]

dentiny opened a new issue, #7377:
URL: https://github.com/apache/opendal/issues/7377

   ### Feature Description
   
   I want end-to-end tracing capability from workload (application which uses opendal for IO operations) to server side (storage backend).
   
   ### Problem and Solution
   
   Suppose users are doing ML checkpointing and their workload has been properly instrumented with otel tracing, I think using tracing layer doesn't inherit the parent span from application.
   
   The reason is, for concurrent operations, we use `TokioExecutor` to spawn a new task for chunk read or write.
   https://github.com/apache/opendal/blob/2a12e2d12e39b882df31e478d999b7db3b44ea01/core/core/src/types/execute/executors/tokio_executor.rs#L27-L29
   
   The easiest workaround could be explicitly passing the current span into the spawned task (though it does break the abstraction layer for opendal, relavent to my another question: https://github.com/apache/opendal/issues/7312)
   ```diff
    impl Execute for TokioExecutor {
        /// Tokio's JoinHandle has its own `abort` support, so dropping handle won't cancel the task.
        fn execute(&self, f: BoxedStaticFuture<()>) {
   -        let _handle = tokio::task::spawn(f);
   +        let span = Span::current();
   +        let _handle = tokio::task::spawn(Instrument::instrument(f, span));
        }
    }
   ```
   
   ### Additional Context
   
   _No response_
   
   ### Are you willing to contribute to the development of this feature?
   
   - [ ] Yes, I am willing to contribute to the development of this feature.


-- 
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: commits-unsubscribe@opendal.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] new feature: end-to-end tracing capability [opendal]

Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
Xuanwo commented on issue #7377:
URL: https://github.com/apache/opendal/issues/7377#issuecomment-4473686466

   Maybe we can wrap the `Execute` inside `TracingLayer`? 


-- 
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: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] new feature: end-to-end tracing capability [opendal]

Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
Xuanwo closed issue #7377: new feature: end-to-end tracing capability
URL: https://github.com/apache/opendal/issues/7377


-- 
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: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org