npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

opentracing-js-ioredis

v2.1.2

Published

Opentracing instrumentation for ioredis

Downloads

130

Readme

Opentracing Redis Node.js Instrumentation

Implements opentracing Redis instrumentation for ioredis node.js client library

Install

yarn add opentracing-js-ioredis

Usage

API

applyInstrumentation(tracer: opentracer.Tracer, redis: Redis, [opts = {}])

Applies instrumentation to Redis client instance, adding methods for seamlessly tracking calls to database

const Redis = require('ioredis');
const opentracing = require('opentracing');
const applyInstrumentation = require('opentracing-js-ioredis');

const tracer = opentracing.Tracer();
const redis = new Redis();
const opts = {
  remoteServiceName: 'redis-production', // defaults to redis
  name: 'traced', // default to `traced`, name of the function that will be attached to `redis`
  tags: {
    [opentracing.Tags.COMPONENT]: 'database', // extra tags that will be attached to spans all the time
  },
  // commands that won't create traces during `.traced` call, listed are defaults.
  // You can only add commands, not remove them. Pipeline command itself is traced, but needs to be blacklisted
  // as it is a special case
  restrictedCommands: [
    'ping',
    'flushall',
    'flushdb',
    'select',
    'auth',
    'info',
    'quit',
    'slaveof',
    'config',
    'sentinel',
    'cluster',
    'swapdb',
    'monitor',
    'pipeline',
  ],
};

// now redis is populated with `.traced` command
applyInstrumentation(tracer, redis, opts);
redis.traced(context: ?Span, commandName: string, ...args: Array): Promise | Void

Invokes commandName and passes args to it, creating a span with commandName and finishing it automatically Parent context is passed via context arg and can be omitted. Make sure you call .finish() whenever it's time to

applyInstrumentation.traceStatements(enabled: boolean)

May be useful for debugging purposes, enables setting tag of opentracing.Tag.DB_STATEMENT to serialized redis command. This is a serious performance hit and is disabled by default as we call command.toWritable twice in that case