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

sivabalan narayanan commented on HUDI-3409:
-------------------------------------------

[~xushiyan] : [~Kalluri]  has shown interest in picking this up. 

btw Rajesh: this is what I am thinking. 

currently metrics are in hudi-client-common. and timeline-server module does 
not depend on this module for now. 

we can probably create a new module called hudi-metrics and move all metrics 
related classes to this one from hudi-client-module.

and make both hudi-client-module and timeline-server-module depend on this new 
one. 

Raymond: let me know if you have better idea to go about this.

 

> Expose Timeline Server Metrics
> ------------------------------
>
>                 Key: HUDI-3409
>                 URL: https://issues.apache.org/jira/browse/HUDI-3409
>             Project: Apache Hudi
>          Issue Type: Improvement
>          Components: timeline-server
>            Reporter: DarAmani Swift
>            Priority: Major
>              Labels: new-to-hudi
>
> Timeline server metrics are pushed to local registry but never going to 
> reporters. Exposing these metrics would greatly improve debugging latency 
> around async processes and timeline server syncs. 
> Metrics are already captured in the [Request 
> Handler|https://github.com/apache/hudi/blob/master/hudi-timeline-service/src/main/java/org/apache/hudi/timeline/service/RequestHandler.java#L527-L531]
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to