-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Instrument Durable Objects #12
Comments
Like #11, an MVP should be the SDK taking the durable object stub, and returning a wrapper with the same fetch interface that makes sure the trace is propagated. I believe the "receive" end should just work as long as it's a normal fetch handler also. |
This may be "done" via #21, but I haven't validated. |
This is likely resolved with 0.6.0, however I'm not sure about the recieving end so keeping this open. |
I'm afraid this won't work for Durable Objects because of slightly different syntax:
So, we canot just simply have |
Maybe as an idea, it makes sense to make public methods to create spans so that Durable Object invocation can at least be manually 'wrapped':
|
Ah darn, I thought it had the same syntax. I forgot it stubbed out. It should still be possible to proxy the stub however 🤔. I could definitely add support for creating spans directly, though it might be a little weird due to the way the SDK currently works. #26 might help make that "just work" |
Hey there 👋
It would be nice if we can instrument the
fetch
call to durable objects.The text was updated successfully, but these errors were encountered: