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

Expose WildFly metrics in /metrics endpoints -------------------------------------------- Key: WFLY-11529 URL: https://issues.jboss.org/browse/WFLY-11529 Project: WildFly Issue Type: Enhancement 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. wildfly_undertow_request_count) and the different supplies should provide labels: {code} wildfly_undertow_request_count{deployment="foo.war", servlet="MyServletA"} 5.0 wildfly_undertow_request_count{deployment="foo.war", servlet="MyServletB"} 10.0 {code} The goal of this issue is to provide metrics for WildFly subsystem and deployments that follows the Prometheus convention. As these conventions is not compatible with MicroProfile Metrics 1.x, these metrics will only be exposed by the HTTP endpoint on /metrics in the Prometheus format (in addition to the base and vendor metrics provided through the microprofile-metrics API).