You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have an integration for symfony but it lacks the tracing for the Symfony messenger component.
I imagine it to be like the LaravelQueueIntegration and see when a worker picked up a message and all traces that happend while processing (e.g. guzzle integration may add some calls).
Is your feature request related to a problem?
No
Describe alternatives you've considered
Keep using my own solution.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thank you for submitting your feature request. While we have yet to estimate a time for implementing this library's instrumentation, we agree that it would be a valuable addition.
I noticed that Symfony auto-instrumentation is already available through OTel, which records spans for Symfony Messenger (open-telemetry/opentelemetry-php-contrib#215). In the meantime, you can use the OTel instrumentation with dd-trace-php support to obtain spans from this library.
Additionally, we encourage external contributions and would be happy to assist anyone with implementing this feature 😊
Describe the feature you'd like
We already have an integration for symfony but it lacks the tracing for the Symfony messenger component.
I imagine it to be like the LaravelQueueIntegration and see when a worker picked up a message and all traces that happend while processing (e.g. guzzle integration may add some calls).
Is your feature request related to a problem?
No
Describe alternatives you've considered
Keep using my own solution.
Additional context
No response
The text was updated successfully, but these errors were encountered: