Redis span ops marked as 'db' instead of 'cache'

[rahul-kumar-saini]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

8.0.0

Framework Version

Node v18.18.2

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

Just initialize Sentry and use ioredis and run some Redis commands.

Expected Result

Redis span ops being cache or cache.[get|set|del] or something.

Actual Result

Redis spans marked as db, which in turn populates the SQL Queries view with Redis commands and makes it less useful. Would be cool to have a dedicated Cache usage view similar to the Queries view where Redis commands could be aggregated instead.

[s1gr1d]

Hello, thanks for writing! We are indeed working on a feature which let's you define specific prefixes for your cache keys. The API will possibly look something like this: integrations: [Sentry.redisIntegration({ cachePrefixes: ['cache:'] })].

If the key is prefixed with one of the defined prefixes, the ops will be marked as cache.[..].

[rahul-kumar-saini]

Hi @s1gr1d! Is there any way for me to also only have certain commands instrumented? Eg let's say I only care for get/set/delete and don't care for other Redis commands?

[s1gr1d]

Currently, there isn't. Would you want to specify certain Redis commands to be instrumented in general or just when you're using Redis as a cache? Meaning, Redis would be instrumented for all commands but only when a key is prefixed with e.g. cache: we would drop commands which are not specified.

[s1gr1d]

If you want, you can already try adding cache prefixes to the integration with the latest version of Sentry. Currently they pick up get and set.