[CASSANDRA-17981] Restore internode custom tracing

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0.8, 4.1.1, 5.0-alpha1, 5.0
• Component/s: Messaging/Internode
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/f01d2b4a3ca114ac58d95befcab3dbbad9d960aa

Test and Documentation Plan

CI

• Assignee: Michael Semb Wever
• Reporter: Piotr Maślanka

Authors

Michael Semb Wever

Reviewers

Aleksey Yeschenko

• Created: 21/Oct/22 08:16
• Updated: 12/Sep/23 13:02
• Resolved: 18/Dec/22 02:38

Description

Title originally was: Ferrying OpenTelemetry span/context via org.apache.cassandra.net.Message.Header

Lately I endeavored to integrate Jaeger with Cassandra. 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.

Issue Links

• is caused by: CASSANDRA-15066 Improvements to Internode Messaging