[
https://issues.apache.org/jira/browse/HUDI-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498619#comment-17498619
]
Rajesh commented on HUDI-3409:
------------------------------
As part of this story I am planning to seperate `{*}hoodie-metrics-common{*}`
module from {*}`hudi-client-common`{*}.
I was originally thinking to move the metrics code into `{*}hudi-common{*}` but
after looking at the code and some discussions, it sounded like more of core
components.
How do we feel about renaming *`hudi-common`* to *`hudi-core`* so that we can
use *`hudi-common`* to cater to the common things like metrics and such.
I am thinking there will be more things like metrics that will need to be
grouped and we will have an explosion of modules if we dont have a
*`hudi-common`* to house them under.
Please let me know what approach we should take here based on your experience
with the codebase.
> 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
> Assignee: Rajesh
> 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)
