Hi all, I want to share the integration plan for OpenTelemetry on the Java Driver side.
In the upcoming patch release (4.19.1), the Java Driver will allow users to inject a request ID into the custom payload of each CQL request (PR <https://github.com/apache/cassandra-java-driver/pull/2037>). This feature represents a significant step toward implementing the context propagation protocol outlined in CEP-32. In the subsequent minor release (4.20.0), the Java Driver will introduce native support for OpenTelemetry (please see the ticket <https://github.com/apache/cassandra-java-driver/pull/2021>, PR <https://github.com/apache/cassandra-java-driver/pull/1994> for proposal, PR <https://github.com/apache/cassandra-java-driver/pull/2021> for implementation). These changes will boost the observability of applications using Cassandra, and will pave the way to CEP-32, so I believe we should not archive the proposal. Best, Jane Jane He c. +1 949 991 8403 w. www.datastax.com <https://www.facebook.com/datastax> <https://twitter.com/datastax> <https://www.linkedin.com/company/datastax/> <https://github.com/datastax/> On Tue, Jul 22, 2025 at 7:49 AM Patrick McFadin <pmcfa...@gmail.com> wrote: > I don't think archiving CEP-32 is the right move, as Josh's point suggests > that it should serve as a placeholder for OTEL in the Cassandra project. > This isn't a topic that will go away. > > What needs to happen in the current version of CEP-32 is an update and > revision to the areas Dinish mentioned. Yuki was the originator of the CEP, > so I think it would be good to hear from him on whether he wants to take up > the revision or hand it off. > > Patrick > > On Mon, Jul 21, 2025 at 6:57 PM guo Maxwell <cclive1...@gmail.com> wrote: > >> I think integrating OpenTelemetry is a great idea. >> >> HBase has already do this thing , see >> https://issues.apache.org/jira/browse/HBASE-25373 . >> >> >> >> >> Josh McKenzie <jmcken...@apache.org> 于2025年7月22日周二 03:46写道： >> >>> I would like to propose extending the scope of the CEP to include C* >>> Sidecar, Analytics, and Java Driver (at a minimum). >>> >>> To clarify (my position, not put words in your mouth Dinesh) - the *CEP* >>> I think should cover them all, but *implementation* we could definitely >>> do piece-meal. >>> >>> On Mon, Jul 21, 2025, at 2:52 PM, Dinesh Joshi wrote: >>> >>> My preference would be to archive it unless there is someone who is >>> interested in actively interested in picking it up. >>> >>> If anybody is interested in picking it up, I would like to propose >>> extending the scope of the CEP to include C* Sidecar, Analytics, and Java >>> Driver (at a minimum). But that is just my 2c. >>> >>> Thanks, >>> >>> Dinesh >>> >>> On Mon, Jul 21, 2025 at 11:17 AM Jindal, Himanshu <himan...@amazon.com> >>> wrote: >>> >>> Hi all, >>> >>> I've been exploring ideas around improving native support for >>> OpenTelemetry in Cassandra and came across CEP-32 >>> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-32>. After >>> reviewing the associated dev mailing list discussions >>> <https://lists.apache.org/thread/oo1kt8s2nyznk5hyfb4kkdmvlgr03ys5>, my >>> understanding is that there isn’t currently a clear path forward for direct >>> OTEL integration. It seems the primary concerns are: >>> >>> 1. The implications of introducing a third-party library into >>> Cassandra, and >>> 2. Potential performance impact on nodes. >>> >>> Is that a fair summary of the current consensus? >>> >>> If so, would it make sense—purely from a CEP hygiene and clarity >>> perspective—to mark CEP-32 as deferred or close it out to reflect the >>> current state? >>> >>> Thanks, >>> Himanshu >>> >>> >>>
