Error with using redis and cloud-trace-nodejs about cloud-trace-nodejs HOT 3 CLOSED

Sorry for the delay in responding...

In terms of disabling the plugin, this can be done from the config:

  /**
   * A list of trace plugins to load. Each field's key in this object is the
   * name of the module to trace, and its value is the require-friendly path
   * to the plugin. (See the default configuration below for examples.)
   * Any user-provided value will be used to extend its default value.
   * To disable a plugin in this list, you may override its path with a falsy
   * value. Disabling any of the default plugins may cause unwanted behavior,
   * so use caution.
   */
  plugins?: {[pluginName: string]: string};

Further down in that same file, you can see the defaultConfig:

export const defaultConfig = {
   // ...
   plugins: {
     // ...
     redis: path.join(pluginDirectory, 'plugin-redis.js')
     // ...
   }
   // ...
}

The request to fix this (and support the latest Redis) is reasonable, but I unfortunately cannot commit to any timeline here due to team capacity constraints. Our team can commit to reviewing pull requests, however. If that is not an option and if this is really, really important to you, escalating this through Cloud Support may help in terms of staffing and prioritization at a higher level.

from cloud-trace-nodejs.

Hey team. Do you need any additional information from me?

from cloud-trace-nodejs.

We'll ensure that cloud-trace-nodejs won't error out when used in conjunction with redis v4+. However, we aren't able to prioritize building actual instrumentation support for redis v4+ at this time. Please consider using @opentelemetry/instrumentation-redis-4 instead.

from cloud-trace-nodejs.