[jboss-jira] [JBoss JIRA] (WFLY-11399) Do not expose WildFly metrics in /metrics endpoints
[
https://issues.jboss.org/browse/WFLY-11399?page=com.atlassian.jira.plugin...
]
Jeff Mesnil updated WFLY-11399:
-------------------------------
Description:
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.
was:
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.
Since
Do not expose WildFly metrics in /metrics endpoints
---------------------------------------------------
Key: WFLY-11399
URL: https://issues.jboss.org/browse/WFLY-11399
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Affects Versions: 15.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Critical
Fix For: 15.0.0.CR1
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)