
Security News
Insecure Agents Podcast: Certified Patches, Supply Chain Security, and AI Agents
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
@opentelemetry/instrumentation-mysql2
Advanced tools
OpenTelemetry instrumentation for `mysql2` database client for MySQL
This module provides automatic instrumentation for the mysql2 module, which may be loaded using the @opentelemetry/sdk-trace-node package and is included in the @opentelemetry/auto-instrumentations-node bundle.
If total installation size is not constrained, it is recommended to use the @opentelemetry/auto-instrumentations-node bundle with @opentelemetry/sdk-node for the most seamless instrumentation experience.
Compatible with OpenTelemetry JS API and SDK 1.0+.
npm install --save @opentelemetry/instrumentation-mysql2
mysql2 versions >=1.4.2 <4OpenTelemetry MySQL2 Instrumentation allows the user to automatically collect trace data and export them to the backend of choice, to give observability to distributed systems when working with mysql2.
To load a specific plugin (MySQL2 in this case), specify it in the registerInstrumentations's configuration
const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
const { MySQL2Instrumentation } = require('@opentelemetry/instrumentation-mysql2');
const { registerInstrumentations } = require('@opentelemetry/instrumentation');
const provider = new NodeTracerProvider();
provider.register();
registerInstrumentations({
instrumentations: [
new MySQL2Instrumentation(),
],
})
You can set the following instrumentation options:
| Options | Type | Description |
|---|---|---|
responseHook | MySQL2InstrumentationExecutionResponseHook (function) | Function for adding custom attributes from db response |
addSqlCommenterCommentToQueries | boolean | If true, adds sqlcommenter specification compliant comment to queries with tracing context (default false). NOTE: A comment will not be added to queries that already contain -- or /* ... */ in them, even if these are not actually part of comments |
maskStatement | boolean | If true, masks the db.statement attribute in spans (default false) with the maskStatementHook |
maskStatementHook | MySQL2InstrumentationMaskStatementHook (function) | Function for masking the db.statement attribute in spans Default: return query.replace(/\b\d+\b/g, '?').replac(/(["'])(?:(?=(\\?))\2.)*?\1/g, '?'); |
This instrumentation implements Semantic Conventions (semconv) v1.7.0. Since then, networking (in semconv v1.23.1) and database (in semconv v1.33.0) semantic conventions were stabilized. As of @opentelemetry/instrumentation-mysql2@0.53.0 support has been added for migrating to the stable semantic conventions using the OTEL_SEMCONV_STABILITY_OPT_IN environment variable as follows:
OTEL_SEMCONV_STABILITY_OPT_IN=http/dup,database/dup to emit both old and stable semantic conventions. (The http token is used to control the net.* attributes, the database token to control to db.* attributes.)OTEL_SEMCONV_STABILITY_OPT_IN=http,database to emit only the stable semantic conventions.By default, if OTEL_SEMCONV_STABILITY_OPT_IN includes neither of the above tokens, the old v1.7.0 semconv is used.
The intent is to provide an approximate 6 month time window for users of this instrumentation to migrate to the new database and networking semconv, after which a new minor version will use the new semconv by default and drop support for the old semconv.
See the HTTP migration guide and the database migration guide for details.
Attributes collected:
| Old semconv | Stable semconv | Description |
|---|---|---|
db.connection_string | Removed | The connection string used to connect to the database. |
db.name | Removed, integrated into the new db.namespace | The name of the database. |
db.system | db.system.name | 'mysql' |
db.statement | db.query.text | The database query being executed. |
db.user | Removed | User used to connect to the database. |
| (not included) | db.namespace | The name of the database, fully qualified within the server address and port. |
net.peer.port | server.port | Remote port number. |
net.peer.name | server.address | Remote hostname or similar. |
Apache 2.0 - See LICENSE for more information.
@opentelemetry/instrumentation-mongodb provides similar functionality for MongoDB as @opentelemetry/instrumentation-mysql2 does for MySQL2. It allows for automatic tracing and collection of telemetry data from MongoDB operations, enabling performance monitoring and analysis.
@opentelemetry/instrumentation-pg offers automatic instrumentation for PostgreSQL using the pg library. Like @opentelemetry/instrumentation-mysql2, it helps in collecting and exporting telemetry data for monitoring and performance analysis of PostgreSQL database operations.
While not an instrumentation package, mysql2 is the underlying library that @opentelemetry/instrumentation-mysql2 instruments. It provides a fast and feature-rich MySQL client for Node.js, and can be used directly for database operations without automatic tracing.
FAQs
OpenTelemetry instrumentation for `mysql2` database client for MySQL
The npm package @opentelemetry/instrumentation-mysql2 receives a total of 4,401,262 weekly downloads. As such, @opentelemetry/instrumentation-mysql2 popularity was classified as popular.
We found that @opentelemetry/instrumentation-mysql2 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.

Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.