Closed dPeS closed 3 weeks ago
Hey @dPeS !
Thanks for bringing this up!
I guess the problem is that the step*()
functions are run in another process or something like this (don't know how Ray works) And that the tracing data are not propagated to the other process thus the spans can not be attached to the transaction you create...
Lets test how much demand there is:
If you want to see us support Ray, please "Thumb up" this issue!
I guess the problem is that the step*() functions are run in another process or something like this (don't know how Ray works) And that the tracing data are not propagated to the other process thus the spans can not be attached to the transaction you create...
@antonpirker not the only problem - in those "remote" ray workers sentry isn't initialized - that's for starter.
@szokeasaurusrex Hey I made PR with Ray integration, it handles tracing propagation to ray cluster, feedback is more than welcome! https://github.com/getsentry/sentry-python/pull/2444
Thanks @glowskir for the integration! We will have a look sometime soon. Can not promise any ETA yet.
@antonpirker is it planned to merge this PR? ray is becoming more and more popular, would be great to use sentry with it.
@leokster Thanks for reaching out, I will try to look into this later this week
@dPeS the Ray integration has been released in Sentry SDK version 2.13.0: https://github.com/getsentry/sentry-python/releases/tag/2.13.0
Thanks again for the great work! 🥇
Problem Statement
https://www.ray.io/
I want to annotate that kind of code with spans:
But I only see one big transaction trace without those 3 spans.
Solution Brainstorm
I think new integration needs to be done.