Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Sep 2015 05:07:04 +0000 (UTC)
From: "mck (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12895978.1443058232000.99225.1443503224687@Atlassian.JIRA>
In-Reply-To: <JIRA.12895978.1443058232000@Atlassian.JIRA>
References: <JIRA.12895978.1443058232000@Atlassian.JIRA>
 <JIRA.12895978.1443058232704@arcas>
Subject: [jira] [Updated] (CASSANDRA-10392) Allow Cassandra to trace to
 custom tracing implementations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mck updated CASSANDRA-10392:
----------------------------
    Description: 
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|].

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.

  was:
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.

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.


> 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
>             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|].
> 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)