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
Describe your environment Hi there, I set up laravel auto-instrumentation. and it is correctly detecting the http request, the calls to DB, but not the jobs.
Steps to reproduce
The entire code is in a docker container here
What is the expected behavior?
I expected to see some spans for the job
What is the actual behavior?
More Context: I have a separate container for the api and the queue worker. The jobs are detected when I set QUEUE_CONNECTION to sync but not when it is set to database
The text was updated successfully, but these errors were encountered:
@ChrisLightfootWild Hi Chris, Thanks for your work on the laravel auto instrumentation package, I am sure I am just misconfiguring something so please if you could point me in the right direction. I would appreaciate🙏.
@ChrisLightfootWild Hi Chris, Thanks for your work on the laravel auto instrumentation package, I am sure I am just misconfiguring something so please if you could point me in the right direction. I would appreaciate🙏.
Thanks for raising the issue. Based on your example repo, it looks like the database driver is being used for your queue. I wonder if this relates to long-running queues again 🤔. If you make several requests to the orders endpoint over a few seconds, I wonder if you might see the batch processor emit some of the telemetry that should be captured.
Describe your environment Hi there, I set up laravel auto-instrumentation. and it is correctly detecting the http request, the calls to DB, but not the jobs.
Steps to reproduce
The entire code is in a docker container here
What is the expected behavior?
I expected to see some spans for the job
What is the actual behavior?
More Context: I have a separate container for the api and the queue worker. The jobs are detected when I set
QUEUE_CONNECTION
to sync but not when it is set to databaseThe text was updated successfully, but these errors were encountered: