[HBASE-26419] Tracing Spans of RPCs should follow otel semantic conventions

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.5.0
• Fix Version/s: 2.5.0, 3.0.0-alpha-3
• Component/s: tracing
• Assignee: Nick Dimiduk
• Reporter: Nick Dimiduk
• Created: 03/Nov/21 23:28
• Updated: 23/Jun/22 12:20
• Resolved: 03/May/22 00:30

Description

The OpenTelemetry project has a conventions document for RPCs that is pretty prescriptive. One thing I noticed is that it requires there be spans named as $package.$service/$method ; we don't do this. We should address this and any other gaps.

Issue Links

• is related to: HBASE-22120 Replace HTrace with OpenTelemetry
• relates to: HBASE-27153 Improvements to read-path tracing
• links to: GitHub Pull Request #3848
• links to: PR master

Sub-Tasks

• Move tracing semantic attributes to their own class: Resolved
• Adhere to semantic conventions regarding table data operations: Resolved
• Introduce `db.hbase.container_operations` span attribute: Resolved
• Implement connection-level attributes: Resolved
• Remove use of `db.hbase.namespace` tracing attribute: Resolved
• Name RPC spans as `$package.$service/$method`: Resolved
• Trace coprocessor exec endpoints: Resolved
• Implement tracing of scan: Resolved
• Improve fidelity of RegionLocator spans: Resolved
• Create module hbase-client-test-support: Resolved
• Traces of async chains result in arbitrarily deep trace stack: Resolved
• Fix trace continuity through CallRunner: Resolved
• Implement generic exception support for TraceUtil methods over Callables and Runnables: Resolved
• Trace a one-shot execution of a Master procedure: Resolved
• Provide meaningful parent spans to ZK interactions: Resolved