feat(node): use ioredis tracing channels#21187
Conversation
Co-Authored-By: GPT-5 Codex <codex@openai.com>
size-limit report 📦
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 93cbcbb. Configure here.
| ); | ||
| setupConnectChannel(CHANNEL_REDIS_CONNECT); | ||
| setupCommandChannel<IORedisCommandData>(CHANNEL_IOREDIS_COMMAND, data => data.args); | ||
| setupBatchChannel<IORedisBatchData>(CHANNEL_IOREDIS_BATCH, () => 'MULTI'); |
There was a problem hiding this comment.
Subscription to nonexistent ioredis:batch channel is dead code
Low Severity
ioredis 5.11 only publishes two tracing channels: ioredis:command and ioredis:connect. There is no ioredis:batch channel — batch metadata (batchMode, batchSize) is included in the ioredis:command context instead. The setupBatchChannel call for CHANNEL_IOREDIS_BATCH, the IORedisBatchData interface, and the corresponding unit tests all exercise a code path that will never be triggered in production, creating a false impression that batch operations receive separate wrapping spans for ioredis.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 93cbcbb. Configure here.


ioredis5.11 released tracing channels so we can start using them in the integration, I followed the same strategy we established withredisclient by limiting the patching to older releases and subscribing anyways which will be inert except for newer releases.I added similar tests as well to ensure both dc and non-dc paths still work.
This is not to be confused with the
redisclient, there is two of them,redisandioredis, the latter being older but more popular.