cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10392) Allow Cassandra to trace to custom tracing implementations
Date Mon, 04 Jan 2016 20:12:40 GMT


Chris Burroughs commented on CASSANDRA-10392:

One minor suggestion:  It would be nice if multiple tracers could be enabled at the same time.
 For example, to use 'normal' tracing to debug a problem *with* a zipkin cluster, or to enable
both zipkin and SOME_OTHER_TRACER for comparison.

> Allow Cassandra to trace to custom tracing implementations 
> -----------------------------------------------------------
>                 Key: CASSANDRA-10392
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: mck
>            Assignee: mck
>             Fix For: 3.x
>         Attachments: 10392-trunk.txt
> It can be possible to use an external tracing solution in Cassandra by abstracting out
the writing of tracing to system_traces tables in the tracing package to separate implementation
classes and leaving abstract classes in place that define the interface and behaviour otherwise
of C* tracing.
> Then via a system property "cassandra.custom_tracing_class" the Tracing class implementation
could be swapped out with something third party.
> An example of this is adding Zipkin tracing into Cassandra in the Summit [presentation|].
Code for the implemented Zipkin plugin can be found at
> In addition this patch passes the custom payload through into the tracing session allowing
a third party tracing solution like Zipkin to do full-stack tracing from clients through and
into Cassandra.

This message was sent by Atlassian JIRA

View raw message