Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Propagate database number, user, and RedisURI into Tracing #2232

Closed
mp911de opened this issue Oct 20, 2022 · 1 comment · Fixed by #3005
Closed

Propagate database number, user, and RedisURI into Tracing #2232

mp911de opened this issue Oct 20, 2022 · 1 comment · Fixed by #3005
Labels
type: feature A new feature
Milestone
Backlog

Comments

@mp911de
Copy link
Collaborator

mp911de commented Oct 20, 2022 •
edited
Loading

It would be neat to have these values to be propagated into the individual tracing integrations.

See also https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/database/#connection-level-attributes
@mp911de mp911de added the type: feature A new feature label Oct 20, 2022
@tishun tishun added this to the Backlog milestone Jun 12, 2024
@thachlp thachlp mentioned this issue Oct 3, 2024
Merged
4 tasks
@thachlp
Copy link
Contributor

thachlp commented Oct 3, 2024

@mp911de @tishun please help review my pr 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: feature A new feature
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

Propagate database number, user, and RedisURI into Tracing thachlp/lettuce
3 participants
@mp911de @tishun @thachlp