@opentelemetry/instrumentation-redis

OpenTelemetry redis Instrumentation for Node.js

This module provides automatic instrumentation for the redis module versions >=2.6.0 <6.

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+.

Installation

npm install --save @opentelemetry/instrumentation-redis

Supported Versions

• redis versions >=2.6.0 <7

Usage

OpenTelemetry Redis 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 redis.

To enable a specific instrumentation, pass it to registerInstrumentations(). This is commonly done via NodeSDK for fully setting up all OpenTelemetry SDK components:

const { NodeSDK } = require('@opentelemetry/sdk-node');
const { RedisInstrumentation } = require('@opentelemetry/instrumentation-redis');

const sdk = new NodeSDK({
  instrumentations: [
    new RedisInstrumentation(),
  ],
});
sdk.start();
process.once('beforeExit', async () => { await sdk.shutdown(); });

See examples/redis for a short example.

Redis Instrumentation Options

Redis instrumentation has a few options available to choose from. You can set the following:

Options	Type	Description
dbStatementSerializer	DbStatementSerializer (function)	Redis instrumentation will serialize the command to the db.statement attribute using the specified function.
responseHook	RedisResponseCustomAttributeFunction (function)	Function for adding custom attributes on db response. Receives params: span, moduleVersion, cmdName, cmdArgs
requireParentSpan	boolean	Require parent to create redis span, default when unset is false.

Custom db.statement Serializer

The instrumentation serializes the command into a Span attribute called db.statement. The standard serialization format attempts to be as informative as possible while avoiding the export of potentially sensitive data. The number of serialized arguments depends on the specific command, see the configuration list in @opentelemetry/redis-common.

It is also possible to define a custom serialization function. The function will receive the command name and arguments and must return a string.

Here is a simple example to serialize the command name and all command arguments. Notice that it might capture sensitive data and big payloads:

const { RedisInstrumentation } = require('@opentelemetry/instrumentation-redis');

const redisInstrumentation = new RedisInstrumentation({
  dbStatementSerializer: function (cmdName, cmdArgs) {
    return [cmdName, ...cmdArgs].join(" ");
  },
});

Semantic Conventions

The instrumentation-redis versions 0.68.0 and later emit the stable v1.33.0+ semantic conventions.

Attribute	Short Description
db.operation.name	Redis command name
db.query.text	The database query being executed
db.system.name	Database identifier; always redis
server.address	Hostname or IP of the connected Redis server
server.port	Port of the connected Redis server

Useful links

• For more information on OpenTelemetry, visit: https://opentelemetry.io/
• For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
• For help or feedback on this project, join us in GitHub Discussions

License

Apache 2.0 - See LICENSE for more information.

Similar packages

Other packages similar to @opentelemetry/instrumentation-redis

redis

The 'redis' package is a popular Redis client for Node.js. While it provides the basic functionality to interact with Redis, it does not offer built-in tracing or telemetry capabilities like @opentelemetry/instrumentation-redis. Developers would need to manually instrument their code to collect telemetry data.

ioredis

The 'ioredis' package is another widely-used Redis client for Node.js, known for its support of advanced Redis features and high performance. Similar to the 'redis' package, it does not include automatic tracing or telemetry features. Developers would need to integrate it with OpenTelemetry manually to achieve similar functionality to @opentelemetry/instrumentation-redis.