[
https://issues.apache.org/jira/browse/CASSANDRA-17981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-17981:
-------------------------------------------
Fix Version/s: 4.0.8
4.1.1
4.2
(was: 4.x)
(was: 4.0.x)
(was: 4.1.x)
Source Control Link:
https://github.com/apache/cassandra/commit/f01d2b4a3ca114ac58d95befcab3dbbad9d960aa
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Restore internode custom tracing
> --------------------------------
>
> Key: CASSANDRA-17981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17981
> Project: Cassandra
> Issue Type: Task
> Components: Messaging/Internode
> Reporter: Piotr Maślanka
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.0.8, 4.1.1, 4.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Title originally was: Ferrying OpenTelemetry span/context via
> org.apache.cassandra.net.Message.Header
> 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: [email protected]
For additional commands, e-mail: [email protected]
