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.

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

Update lettuce-5.0 to Instrumenter API #3125

Merged
merged 1 commit into from
May 31, 2021
Merged

Update lettuce-5.0 to Instrumenter API #3125

merged 1 commit into from
May 31, 2021

Conversation

trask
Copy link
Member

@trask trask commented May 29, 2021

No description provided.

"$SemanticAttributes.NET_PEER_PORT.key" incorrectPort
"$SemanticAttributes.DB_SYSTEM.key" "redis"
"$SemanticAttributes.DB_STATEMENT.key" "CONNECT"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we hard code at least operation == CONNECT in the instrumentation?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or perhaps we're fine with it being the span name, given there's no Redis command named connect. That makes sense actually

@trask trask merged commit 7d46c33 into open-telemetry:main May 31, 2021
@trask trask deleted the lettuce-5.0-to-instrumenter-api branch May 31, 2021 14:49
robododge pushed a commit to robododge/opentelemetry-java-instrumentation that referenced this pull request Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants