-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tracing] Swift Distributed Tracing support (or better async/await support) #1511
Comments
Thanks for suggestion @0xpablo and the example, very helpful. We have been talking to support structured concurrency within the team already. To your point on adopting/providing https://github.com/apple/swift-distributed-tracing support, we usually stay close to Otel (and Open Tracing) in terms of experience (I know it is not 1:1 mapping), but that's the aspiration. I wonder, if |
That's great to hear! I think it would make sense to make OTSpan Sendable to be able to pass it around different concurrency domains. I think this should be easy as DDSpan can be marked as Thanks! |
Mostly yes, DDSpan can be marked as |
Do we have any updates on this ticket? |
I was looking to integrate DataDog's tracing today and I noticed there's a concept of the current execution context but I believe it's using the os_activity APIs based on threads, which doesn't work with code using async/await.
It would be great to either support Swift Distributed Tracing or to at least have better async/await support using Task Locals.
The text was updated successfully, but these errors were encountered: