-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support tracing in Cassandra itself #1
Comments
As I understand from https://github.com/thelastpickle/cassandra-zipkin-tracing
It will work only starting with Cassandra 3.4. Current is 3.10 |
That's my understanding as well. Hopefully the plugin can be purely OpenTracing, so that it would work with any tracer. It could use service loader. |
service loader requires adding file under "META-INF/service" with interface name (as filename) and implementation (in file content). |
@malafeev The cassandra custom tracing class simply needs to use https://github.com/opentracing-contrib/java-tracerresolver - this uses service loader under the covers, so as long as the tracer provides the TracerResolver impl (and any relevant config) it will just work by adding the dependency to the cassandra server. |
looks like LightStep tracer doesn't provide TracerResolver. @bhs ? |
Not sure about Lightstep. Jaeger does support tracer resolver |
@malafeev, LightStep's tracer does not provide TracerResolver, but that is not intentional and easily remedied... we just haven't had a customer asking for it. |
I faced one issue: payload is sent using ByteBuffer. tracer.inject(span.context(), Builtin.BINARY, ByteBuffer.allocate(????????)); |
@malafeev just wanted to make sure you were aware of opentracing/opentracing-java#99 (which should be part of the 1.0 release, I'd argue). |
Latest BINARY proposal: opentracing/opentracing-java#276 |
It would be nice if this module not only wrapped Cassandra calls in the client-side spans, but would also inject the opentracing span context into Cassandra requests so that tracing of the Cassandra backend was also possible, e.g. as was done in this blog post.
The text was updated successfully, but these errors were encountered: