Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/XSAM/otelsql below:

XSAM/otelsql: OpenTelemetry instrumentation for database/sql

It is an OpenTelemetry instrumentation for Golang database/sql, a port from open-telemetry/opentelemetry-go-contrib#505.

It instruments traces and metrics.

$ go get github.com/XSAM/otelsql

This project provides four different ways to instrument database/sql:

otelsql.Open, otelsql.OpenDB, otesql.Register and otelsql.WrapDriver.

And then use otelsql.RegisterDBStatsMetrics to instrument sql.DBStats with metrics.

db, err := otelsql.Open("mysql", mysqlDSN, otelsql.WithAttributes(
	semconv.DBSystemMySQL,
))
if err != nil {
	panic(err)
}
defer db.Close()

err = otelsql.RegisterDBStatsMetrics(db, otelsql.WithAttributes(
	semconv.DBSystemMySQL,
))
if err != nil {
	panic(err)
}

Check Option for more features like adding context propagation to SQL queries when enabling WithSQLCommenter.

See godoc for details.

Getting started with otelsql, the OpenTelemetry instrumentation for Go SQL, is a blog post that explains how to use otelsql in miutes.

This project provides two docker-compose examples to show how to use it.

• The stdout example is a simple example to show how to use it with a MySQL database. It prints the trace data to stdout and serves metrics data via prometheus client.
• The otel-collector example is a more complex example to show how to use it with a MySQL database and an OpenTelemetry Collector. It sends the trace data and metrics data to an OpenTelemetry Collector. Then, it shows data visually on Jaeger and Prometheus servers.

The environment variable OTEL_SEMCONV_STABILITY_OPT_IN will be supported for at least six months. After this period, support for legacy metrics and Semantic Conventions v1.24.0 may be removed in the next release.

Check the CHANGELOG.md for more details.

It creates spans on corresponding methods.

Use SpanOptions to adjust creation of spans.

The instrumentation supports different OpenTelemetry semantic convention stability levels, configured through the OTEL_SEMCONV_STABILITY_OPT_IN environment variable:

Two types of metrics are provided depending on the semantic convention stability setting:

• db.sql.latency: The latency of calls in milliseconds
  • Unit: milliseconds
  • Attributes: method (method name), status (ok, error)

• db.client.operation.duration: Duration of database client operations
  • Unit: seconds
  • Attributes: db.operation.name (method name), error.type (if error occurs)

• db.sql.connection.max_open: Maximum number of open connections to the database
• db.sql.connection.open: The number of established connections
  • Attributes: status (idle, inuse)
• db.sql.connection.wait: The total number of connections waited for
• db.sql.connection.wait_duration: The total time blocked waiting for a new connection (ms)
• db.sql.connection.closed_max_idle: The total number of connections closed due to SetMaxIdleConns
• db.sql.connection.closed_max_idle_time: The total number of connections closed due to SetConnMaxIdleTime
• db.sql.connection.closed_max_lifetime: The total number of connections closed due to SetConnMaxLifetime

The instrumentation supports different OpenTelemetry semantic convention stability levels, configured through the OTEL_SEMCONV_STABILITY_OPT_IN environment variable:

Connection statistics metrics (db.sql.connection.*) are always emitted regardless of the stability setting.

This allows users to gradually migrate to the new OpenTelemetry semantic conventions while maintaining backward compatibility with existing dashboards and alerts.

When errors occur during database operations, the error.type attribute is automatically populated with the type of the error. This provides more detailed information for debugging and monitoring:

1. For standard driver errors: Special handling for common driver errors:

   • database/sql/driver.ErrBadConn
   • database/sql/driver.ErrSkip
   • database/sql/driver.ErrRemoveArgument

2. For custom errors: The fully qualified type name is used (e.g., github.com/your/package.CustomError).

3. For built-in errors: The type name is used (e.g., *errors.errorString for errors created with errors.New()).

Note: The error.type attribute is only available when using the new stable OpenTelemetry semantic convention metrics. This requires setting OTEL_SEMCONV_STABILITY_OPT_IN to either database/dup or database. With the default setting (empty), which only uses legacy metrics, the error.type attribute will not be populated.

This project is tested on the following systems.

While this project should work for other systems, no compatibility guarantees are made for those systems currently.

The project follows the Release Policy to support major Go releases.

Based on this comment, OpenTelemetry SIG team like to see broader usage and community consensus on an approach before they commit to the level of support that would be required of a package in contrib. But it is painful for users without a stable version, and they have to use replacement in go.mod to use this instrumentation.

Therefore, I host this module independently for convenience and make improvements based on users' feedback.

I use GitHub discussions/issues for most communications. Feel free to contact me on CNCF slack.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4