[
https://issues.apache.org/jira/browse/HBASE-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254113#comment-17254113
]
Duo Zhang commented on HBASE-25424:
-----------------------------------
Started a jaeger all-in-one server locally, and changed the options to
{code}
# Uncomment to enable trace, you can change the options to use other exporters
such as jaeger or
# zipkin
export HBASE_TRACE_OPTS="-Dotel.config.sampler.probability=0.1
-Dotel.exporter=jaeger -Dotel.exporter.jaeger.service.name=hbase"
{code}
We can see some trace information now. Let me upload the image. Not very
familiar with jaeger actually...
> 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
>
> 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)
