[
https://issues.apache.org/jira/browse/HBASE-26241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-26241:
------------------------------
Attachment: s3.jpg
s2.jpg
s1.jpg
> Showcase/document a end-to-end tracing integreated with an external sink e.g.
> Jaeger or zipkin
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-26241
> URL: https://issues.apache.org/jira/browse/HBASE-26241
> Project: HBase
> Issue Type: Task
> Components: tracing
> Affects Versions: 3.0.0-alpha-1, 2.5.0
> Reporter: Tak-Lon (Stephen) Wu
> Priority: Major
> Attachments: s1.jpg, s2.jpg, s3.jpg
>
>
> This task/issue was being discussed [in the vote of
> HBASE-25853|https://lists.apache.org/thread.html/rb36f0b6b179ee5f42cff7bb60de2797f69c450752c993f0b1e0f6118%40%3Cdev.hbase.apache.org%3E]
>
> bq. I've not seen anyone report their success at integrating these changes
> into a telemetry system and showing end-to-end tracing of a service call. As
> I recall from the last 2.5 discuss thread, we wanted this to be the banner
> feature for the minor release. Since we don't have this end-to-end
> confirmation, do we have someone who's volunteered to demonstrate that final
> proof-of-integration in a timely manner? Perhaps that someone is keen to be
> release manager for 2.5.
> What a `service call` mean ? (pending discussion on above email exchange or
> on this JIRA)
> e.g. for RPCclient/AbstractRpcClient, it trace at the
> AbstractRpcClient#callMethod level with a span of `RpcClient.callMethod` . or
> whenever a connection is closed, it will emit `AsyncConnection.close`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
