[jboss-jira] [JBoss JIRA] (WFLY-11335) Fix Undertow Deployment Metrics
Jeff Mesnil (Jira)
issues at jboss.org
Tue Nov 13 07:10:00 EST 2018
[ https://issues.jboss.org/browse/WFLY-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mesnil updated WFLY-11335:
-------------------------------
Description:
Undertow deployment metrics are relevant only when /subsystem=undertow's statistics-enabled is true.
When that it not the case (and metrics can not be computed) the metrics' read handler should not return a meaningless value (e.g. 0) as it already specifies an undefined metric value in the metrics' attribute definition.
That change and WFCORE-4190 will prevent exposing Undertow metrics when they do not report actual metric from Undertow underlying runtime.
was:
Undertow metrics are relevant only when /subsystem=undertow's statistics-enabled is true.
When that it not the case (and metrics can not be computer) the metrics' read handler should not return a meaningless value (e.g. 0) as it already specifies an undefined metric value in the metrics' attribute definition.
That change and WFCORE-4190 will prevent exposing Undertow metrics when they do not report actual metric from Undertow underlying runtime.
> Fix Undertow Deployment Metrics
> -------------------------------
>
> Key: WFLY-11335
> URL: https://issues.jboss.org/browse/WFLY-11335
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
> Fix For: 15.0.0.Beta1
>
>
> Undertow deployment metrics are relevant only when /subsystem=undertow's statistics-enabled is true.
> When that it not the case (and metrics can not be computed) the metrics' read handler should not return a meaningless value (e.g. 0) as it already specifies an undefined metric value in the metrics' attribute definition.
> That change and WFCORE-4190 will prevent exposing Undertow metrics when they do not report actual metric from Undertow underlying runtime.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list