-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add db.redis.arguments
for requests and responses
#2908
Comments
Hey @haddasbronfman - would you mind mentioning examples/use cases? |
Hi, sure: example 2 - example 3 - example 4 - example 5 - |
Does this need to be Redis specific? I see for example a very similar request that is more generic: https://cloud-native.slack.com/archives/C01N7PP1THC/p1668007675690439 |
I wrote it specifically for Redis, but you're right there might be more databases that this attribute can fit to. |
See if you can generalize it and make applicable to other database and name appropriately (e.g. |
So in theory we should be reporting the arguments as part of the statement, as per the Spec:
So we should poke the instrumentation authors. @haddasbronfman what instrumentation/language/version are you using? |
@carlosalberto you're right. I opened this issue: open-telemetry/opentelemetry-js-contrib#1294 |
What are you trying to achieve?
I want to add to the database semantic conventions additional attributes for
redis
spans.The value of adding the metadata is to help users get more information from the traces which could allow for easier troubleshooting.
I propose the following names for the attribute:
db.redis.arguments
The text was updated successfully, but these errors were encountered: