[
https://issues.apache.org/jira/browse/HBASE-26419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516365#comment-17516365
]
Andrew Kyle Purtell commented on HBASE-26419:
---------------------------------------------
Thanks for the heads' up [~ndimiduk] . Glad to hear it.
We sorted most of the issues with log4j2 landing on the branch, the one
remaining that I know of is HBASE-26854.
I need to document my compression codec work, that's HBASE-26330.
HBASE-26192 is a nice to have but not critical, but now is time for me to pick
it up.
Then we are good to go, I think.
> Tracing Spans of RPCs should follow otel semantic conventions
> -------------------------------------------------------------
>
> Key: HBASE-26419
> URL: https://issues.apache.org/jira/browse/HBASE-26419
> Project: HBase
> Issue Type: Improvement
> Components: tracing
> Affects Versions: 3.0.0-alpha-1, 2.5.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Blocker
> Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> The OpenTelemetry project has a [conventions
> document|https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/rpc.md]
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
