cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-10392) Allow Cassandra to trace to custom tracing implementations
Date Wed, 24 Feb 2016 18:31:18 GMT


T Jake Luciani edited comment on CASSANDRA-10392 at 2/24/16 6:31 PM:

committed in {{bf25e668f416b1c279986d1b23fee2a0192d8022}}


was (Author: tjake):
committed in {bf25e668f416b1c279986d1b23fee2a0192d8022}


> Allow Cassandra to trace to custom tracing implementations 
> -----------------------------------------------------------
>                 Key: CASSANDRA-10392
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: mck
>            Assignee: mck
>             Fix For: 3.4
>         Attachments: 10392-trunk.txt, cassandra-dtest_master-10392.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