You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "mck (JIRA)" <ji...@apache.org> on 2015/09/24 03:31:04 UTC

[jira] [Created] (CASSANDRA-10392) Allow Cassandra to trace to custom tracing implementations

mck created CASSANDRA-10392:
-------------------------------

             Summary: Allow Cassandra to trace to custom tracing implementations 
                 Key: CASSANDRA-10392
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10392
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: mck
            Assignee: mck


It can be possible to use in external tracing solutions in Cassandra by abstracting out the tracing->system_traces tables in the tracing package to separate implementation classes.

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.

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.


There's still a few todos and fixmes in the initial patch but i'm submitting early to get feedback.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)