-
Notifications
You must be signed in to change notification settings - Fork 550
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
mysql2 seems to put the first query in it's own span when using a pool #1050
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
unstale |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Really? |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
🫥 |
What version of OpenTelemetry are you using?
What version of Node are you using?
v16.12.0
What did you do?
My Config
What did you expect to see?
I expected all traces to have the same traceId
What did you see instead?
I noticed that the first MySQL query trace uses it's own id. FWIW, were using pools
Additional context
First call
Second call
The text was updated successfully, but these errors were encountered: