You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2022/04/01 11:54:00 UTC
[jira] [Commented] (HBASE-26419) Tracing Spans of RPCs should follow otel semantic conventions
[ https://issues.apache.org/jira/browse/HBASE-26419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515885#comment-17515885 ]
Nick Dimiduk commented on HBASE-26419:
--------------------------------------
Head's up [~apurtell] the scan tracing patches have landed. At this point, I think tracing is good enough for a 2.5.0. I'll continue working through the subtasks, but I'm fine if we make them improvements that ship in subsequent patch releases.
> 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)