[
https://issues.apache.org/jira/browse/HBASE-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253990#comment-17253990
]
ramkrishna.s.vasudevan commented on HBASE-25424:
------------------------------------------------
bq.And on enable/disable trace on the fly, theoretically we could do this, as
the OpenTelemetrySdk has a method to update trace config, and we could also
reset the global OpenTelemetrySdk at runtime.
Right this is what we did in our POC. Just exposed a command at the shell which
will go and enable the tracing at a given RS by changing the global tracer at
runtime. How ever in poc we did not trace from client to server. Just the
server side path.
bq.[https://github.com/open-telemetry/opentelemetry-java-instrumentation]
I see. I did not come across this one. Our own module might be better till this
opentelemetry and its allied projects become GA?
> 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)
