[jboss-jira] [JBoss JIRA] (WFLY-11529) Expose WildFly metrics in /metrics endpoints

[Jeff Mesnil (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil updated WFLY-11529:
-------------------------------
    Priority: Major  (was: Critical)


> Expose WildFly metrics in /metrics endpoints
> --------------------------------------------
>
>                 Key: WFLY-11529
>                 URL: https://issues.jboss.org/browse/WFLY-11529
>             Project: WildFly
>          Issue Type: Bug
>          Components: MP Metrics
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> MicroProfile Metrics mandates that metrics names are unique and does not able to have multiple suppliers for the same metric with different labels.
> Due to this restriction, the names of WildFly metrics are long and convoluted; e.g. `deployment/example.war/subsystem/undertow/servlet/org.example.MyServlet/request-count`
> This type of names prevents any aggregation in Prometheus and is very different from the names configured in the imx-exporter for older WildFly versions (https://github.com/jboss-openshift/cct_module/pull/314)
> Instead, the name of the metric should be "simple" (e.g. undertow_request_count) and the different supplies should provide labels:
> {code}
> undertow_request_count{deployment="foo.war", servlet="MyServletA"} 5.0
> undertow_request_count{deployment="foo.war", servlet="MyServletB"} 10.0
> {code}
> In its current state the WildFly metrics are not usable and we should disable them until they are properly exposed in a correct state.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)