[
https://issues.apache.org/jira/browse/HBASE-26531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492600#comment-17492600
]
Duo Zhang commented on HBASE-26531:
-----------------------------------
This is not covered by the spec of OTel I suppose, so we are free to implement
our own solution.
For me, I think we'd better keep the rpc span name unchanged, as this is what
we actually called through rpc.
And for metadata or a new span, looking at the code, there is a
service.callMethod call explicitly in our code, so I prefer we use the new span
way.
Thanks.
> Trace coprocessor exec endpoints
> --------------------------------
>
> Key: HBASE-26531
> URL: https://issues.apache.org/jira/browse/HBASE-26531
> Project: HBase
> Issue Type: Sub-task
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> Decide how to trace Coprocessor Exec endpoints. They either look like table
> operations OR generic RPC calls... I'm guessing the latter, but will give it
> some study.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
