You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2022/10/21 15:26:00 UTC
[jira] [Assigned] (CASSANDRA-17981) Ferrying OpenTelemetry span/context via org.apache.cassandra.net.Message.Header
[ https://issues.apache.org/jira/browse/CASSANDRA-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever reassigned CASSANDRA-17981:
----------------------------------------------
Assignee: Michael Semb Wever
> Ferrying OpenTelemetry span/context via org.apache.cassandra.net.Message.Header
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-17981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17981
> Project: Cassandra
> Issue Type: Task
> Reporter: Piotr Maślanka
> Assignee: Michael Semb Wever
> Priority: Normal
>
> 0
> Lately I endeavored to integrate [Jaeger with Cassandra|https://github.com/smok-serwis/cassandra-jaeger-tracing]. However, the only way to reliably sent messages across modes requires specifying a ParamType, which is limited only to an UUID, which is not enough to sent both the 128-bit spanId and parent, nevermind the baggage.
> Is there any other way I can reliably send the data to other node using Message.Header?
> Or could I alternatively coordinate with the Cassandra team to reserve an integer for the definite use of ferrying OpenTelemetry data?
> I'v detailed my endeavors [here|https://henrietta.com.pl/index.php/2022/10/19/how-do-you-integrate-custom-tracing-with-cassandra/].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org