Issue with 3.11.5 mysql2 span not being generated

[liustve]

What version of OpenTelemetry are you using?

0.54.0 (latest)

What version of Node are you using?

v22.10.0

What did you do?

Set up an express server to make a call to a dummy nonexistant database using mysql2:
import mysql from 'mysql2';

const connection = mysql.createConnection({
host: process.env.DB_HOST,
user: process.env.DB_USER,
password: process.env.DB_PASSWORD
});

connection.query(
'CREATE DATABASE IF NOT EXISTS db',
(err, results) => {
if (err) {
console.error('Error creating database:', err);
return;
}
console.log('Database created successfully');
}
);

Ran using version 3.11.4, db span exists and gets populated:

Ran using version 3.11.5, no db span:

What did you expect to see?

DB span to populate in newest mysql2 version

What did you see instead?

No span running on the latest mysql2 version and latest otel js version.

Additional context

Related issue: aws-observability/aws-otel-js-instrumentation#127

[pichlermarc]

huh, weird - I thought this was fixed in #2579

[pichlermarc]

@liustve thanks for reaching out - assigning P2 (incomplete or missing telemetry).

[david-luna]

Hi @liustve

I've tried to reproduce the issue with no luck in this small project. For both versions of mysql2 (3.11.4 & 3.11.5) the instrumentation gets the db statement.

When you mention the version 0.54.0 (latest) which package are you referring to? I?m asking because there are several packages involved in the tracing setup.

this is the list of dependencies of the project

npm ls
[email protected] /Users/david/Documents/repos/dl/otel-js-contrib-2590
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @opentelemetry/[email protected]
├── @types/[email protected]
├── [email protected]
├── [email protected]
└── [email protected]

could yo give me some directions on hot to reproduce the issue?

[liustve]

Hi David, the package that I was using for this issue is v0.54.0:
https://www.npmjs.com/package/@opentelemetry/auto-instrumentations-node

The instrumentation I was using for mysql2 matches your version (0.44.0).
Would it be possible to set up a time to do a live debugging sometime next week?

Thanks!

[alexa-gt]

Can reproduce. Downgrading mysql2 fixed it for me.

Edit: [email protected] works for me.

[david-luna]

@liustve @alexa-gt I've updated the small project mentioned in #2590 (comment) to use auto instrumentations and the CLI option to register it. I'm still seeing the span being sent to the collector. Could you provide a more complete example to reproduce the error? Is that call to a nonexistant DB inside an express middleware perhaps?

[alexa-gt]

Nope, it exists and is in an express handler. As attached with latest mysql2 version.

As requested, otel_poc.zip

@david-luna Can I see your package.json and package-lock.json?

[macno]

huh, weird - I thought this was fixed in #2579

Hi @pichlermarc your fix seems to work only importing from mysql2 "directly" but not if you are importing from mysql2/promise

@david-luna that's why you don't replicate in your project

To reproduce you can use https://github.com/macno/otel-js-contrib-2590