You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2020/12/24 10:38:00 UTC
[jira] [Resolved] (HBASE-25424) Find a way to config OpenTelemetry
tracing without directly depending on opentelemetry-sdk
[ https://issues.apache.org/jira/browse/HBASE-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-25424.
-------------------------------
Fix Version/s: HBASE-22120
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to branch HBASE-22120.
Thanks [~zghao] for reviewing.
> Find a way to config OpenTelemetry tracing without directly depending on opentelemetry-sdk
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-25424
> URL: https://issues.apache.org/jira/browse/HBASE-25424
> Project: HBase
> Issue Type: Sub-task
> Components: dependencies, tracing
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: HBASE-22120
>
> Attachments: jaeger.png
>
>
> According to the document of OpenTelemetry, for all the modules which could be depended by downstream users, we should only depend on opentelemetry-api.
> But the open telemetry propagator must be initialized programmatically, so we need to have a module to implement the code and introduce dependency on opentelemetry-sdk, and we need to call it before doing anything when starting master, regionserver, and so on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)