Re: tracing improvements

I do miss this from other RDBMSs. If you could come up with a light-touch way to do this, I think a lot of people would be quite happy about it. On Wed, Jan 25, 2017 at 2:02 PM, Corentin Chary wrote: > On Wed, Jan 25, 2017 at 9:55 PM, Sam Overton

Re: tracing improvements

I think all three of these have merit. Per-CF tracing would be the most immediately useful (and likely least impactful). For #3, I like the interface approach over exposing internal APIs. You can sort of kind of do this with custom QueryProcessor, but having something specific to tracing would be

Re: tracing improvements

On Wed, Jan 25, 2017 at 9:55 PM, Sam Overton wrote: > Hello cassandra-dev, > > I would like to continue the momentum on improving Cassandra's tracing, > following Mick's excellent work on pluggable tracing and Zipkin support. > > There are a couple of areas we can improve

tracing improvements

Hello cassandra-dev, I would like to continue the momentum on improving Cassandra's tracing, following Mick's excellent work on pluggable tracing and Zipkin support. There are a couple of areas we can improve that would make tracing an even more useful tool for cluster operators to diagnose