[ 
https://issues.apache.org/jira/browse/HDDS-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806774#comment-16806774
 ] 

Elek, Marton commented on HDDS-1153:
------------------------------------

q. I think that's a good idea, Wei-Chiu Chuang, I created HDDS-1364 for it.

+1. Thanks the idea [~jojochuang] and to create the issue [~knanasi]. I can see 
some limitations of the web ui of Jaeger and interested to see what can we do 
with Zipkin (I would like to get more statistical data about the reported spans 
and sub-spans)

> Make tracing instrumentation configurable
> -----------------------------------------
>
>                 Key: HDDS-1153
>                 URL: https://issues.apache.org/jira/browse/HDDS-1153
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Elek, Marton
>            Assignee: Kitti Nanasi
>            Priority: Major
>              Labels: newbie, pull-request-available
>         Attachments: HDDS-1153.001.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> TracingUtil.createProxy is a helper method to create a proxy instance with 
> tracing support.
> The proxy instance implements the same interface as the original class and 
> delegates all the method calls to the original instance but it also sends 
> tracing information to the tracing server.
> By default it's not a big overhead as the tracing libraries can be configured 
> to send tracing only with some low probability.
> But to make it more safe we can make it optional. With a global 
> 'hdds.tracing.enabled' configuration variable (can be true by default) we can 
> adjust the behavior of TracingUtil.createProxy.
> If the tracing is disabled the TracingUtil.createProxy should return with the 
> 'delegate' parameter instead of a proxy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to