Skip to content

Conversation

@aryamohanan
Copy link
Contributor

@aryamohanan aryamohanan commented Dec 5, 2025

Which problem is this PR solving?

Closes #3082.

The instrumentation was using older semantic conventions and did not populate db.operation.name.
Additionally, commands in MULTI/EXEC and pipeline were not identified correctly

Short description of the changes

  • Set db.operation.name when the latest semantic conventions are enabled.
  • Added MULTI and PIPELINE prefixes for commands executed in transactions or pipelines.

@aryamohanan aryamohanan requested a review from a team as a code owner December 5, 2025 12:59
@aryamohanan aryamohanan changed the title fix(instrumentation-redis): correctly mark MULTI/PIPELINE in operation name fix(instrumentation-ioredis): correctly mark MULTI/PIPELINE in operation name Dec 5, 2025
@aryamohanan aryamohanan force-pushed the fix-ioredis-multi-command branch from e9276f8 to 96ccbb5 Compare December 5, 2025 13:58
@aryamohanan aryamohanan force-pushed the fix-ioredis-multi-command branch from 96ccbb5 to 714043c Compare December 5, 2025 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[instrumentation-redis and ioredis] multi/pipeline spans are not marked as such

3 participants