Support configuring skipRawCommand via environment variable for Redis instrumentation

[laststem]

I’m using dd-trace-go with orchestrion (auto-instrumentation) and noticed that there is currently no way to enable skipRawCommand without using the manual Redis instrumentation API.

In contrib/redis/go-redis.v9/option.go, skipRawCommand can only be configured via code-level options (e.g. WithSkipRawCommand(true)), which works for manual instrumentation but is not accessible when using orchestrion, since Redis clients are auto-instrumented at runtime.

This causes an issue where Redis commands like:

GET <sensitive-key>

are captured in APM spans (e.g. redis.raw_command or resource names), potentially leaking sensitive information such as tokens, user identifiers, or secrets.

Why this matters

• Orchestrion users cannot control Redis instrumentation options in code
• Redis keys often contain PII or secrets
• Relying solely on Agent-side obfuscation is possible, but:
  • Requires newer Agent versions
  • Is less discoverable for Go users
  • Removes flexibility at the tracer level

Proposal

Add support for configuring skipRawCommand via an environment variable, for example:

DD_TRACE_REDIS_SKIP_RAW_COMMAND=true (default: false)

This would:

• Allow orchestrion users to safely disable raw Redis command capture
• Align Redis instrumentation with other tracer features that support env-based configuration
• Improve security by default for Redis usage with sensitive keys

Happy to help with testing or implementation details if needed.
Thanks for the great work on dd-trace-go!

[darccio]

We've opened a PR for this: #4389

[darccio]

It was merged. It'll be released as part of v2.7.0, this month's release.