-
Notifications
You must be signed in to change notification settings - Fork 870
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
ClickHouse HTTP client instrumentation does not work when no database selected #11851
Comments
I believe the issue here is the instrumentation is not properly handling the case where a database name is not passed in via the connection string. I was able to reproduce the issue by running:
I then identified the exception stack trace:
And by adding debug logs into the instrumentation identified that it is the I then tried again with the database included in the connection string:
And everything worked as expected: I will work on a fix for this |
Fix confirmed: Instrumentation of ClickHouse Java HTTP Client 0.6.2 with OpenTelemetry Java Agent 2.7.0 gives me insight into ClickHouse operations above the HTTP level and creates spans with |
Describe the bug
OpenTelemetry JavaAgent 2.6.0 should add instrumentation to the ClickHouse JavaAgent. I tried it with our application (Java 11, Clojure 1.11.3, ClickHouse HTTP Client 0.6.2, using the built-in Java HTTP Client). As with previous JavaAgent versions, I only see the spans created by
io.opentelemetry.java-http-client
.Steps to reproduce
POST
, but no ClickHouse client span.I looked at the traces using OpenTelemetry Collector ingesting into Grafana Tempo, and using https://github.com/dotnet/aspire/tree/main/src/Aspire.Dashboard locally, but both only show the
io.opentelemetry.java-http-client
spans.Expected behavior
I expected to see two nested spans, one created by the ClickHouse client instrumentation, the other created by the HTTP client instrumentation.
Actual behavior
I only see a HTTP client span with name
POST
, but no ClickHouse client span.Javaagent or library instrumentation version
v2.6.0
Environment
JDK:
OS:
Additional context
This continues #11660 (comment).
The text was updated successfully, but these errors were encountered: