[
https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
T Jake Luciani resolved CASSANDRA-10392.
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.4
committed in {bf25e668f416b1c279986d1b23fee2a0192d8022}
Thanks!
> 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
> 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|http://thelastpickle.com/files/2015-09-24-using-zipkin-for-full-stack-tracing-including-cassandra/presentation/tlp-reveal.js/tlp-cassandra-zipkin.html].
> Code for the implemented Zipkin plugin can be found at
> https://github.com/thelastpickle/cassandra-zipkin-tracing/
> 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
(v6.3.4#6332)
