October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4190) Distinguish undefined metric value

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4190?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4190: -------------------------------- Priority: Critical (was: Major) > Distinguish undefined metric value > ---------------------------------- > > Key: WFCORE-4190 > URL: https://issues.jboss.org/browse/WFCORE-4190 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > WildFly resources can registered metrics for runtime read-only attributes whose value change during server activity. > Some of these metrics are "disabled" by default (as they may be expensive to compute) and are enabled using a boolean attribute named statistics-enabled in their resource tree. > When these metrics would not be able to compute their value, they could register a "undefined metric value" that would be returned by the :read-attribute handler if the metric read handler would return an undefined value. > This causes a significant issue when one observes WildFly as it generates metrics figures that gives an incorrect observation of the server activity. > Typical example is undertow metrics to see bytes sent and received on its http(s)-listeners[1]. > When the metric is defined[2], it specifies an undefined metric value of 0. > From the outside, when a monitoring tool will fetch value for the bytes-sent metric, it may return 0 in 2 different cases: > * the metric is not enabled if the statistics-enabled attribute at [3] is false (which is the case by default). This does not mean that there is no network traffic. > * statistics-enabled is true but there is no network traffic on the HTTP listener > These 2 cases are wildly different but it is not possible to distinguish between them > In order to distinguish these 2 cases, the :read-attribute operation (and by extension the :read-resource operation) will be enhanced with a "include-undefined-metric" operation parameter. > This parameter is taken into account only for metric attribute: > * if include-undefined-metric is true, the operation will return a undefined value from the metric's read handler *without substituting it by the *undefined metric value* from the metric AttributeDefinition > * if the flag is false (by default), the current behaviour is used (if the read handler returns an undefined value, uses the *undefined metric value* from the metric AttributeDefinition. > This will allow external monitoring tool (as well as the metrics subsystem from WFLY-10712) to know that the metric does not return a meaningful value. > When I looked at various metrics registered in WildFly, some of them returns a meaningless value if the runtime code can not compute the value (e.g. Undertow statistics returns 0 if they are not able to obtain the underlying statistics[4]) in addition to defined an "undefined metric value" from the metric AttributeDefinition. > These read handlers would have to be fixed so they MUST NOT return a defined value that does not correspond to the actual value required by the operation. > [1] http://wildscribe.github.io/WildFly/14.0/subsystem/undertow/server/http-l... > [2] https://github.com/wildfly/wildfly/blob/8f620bbe6d481c9c2c6422e2250326a98... > [3] http://wildscribe.github.io/WildFly/14.0//subsystem/undertow/index.html#a... > [4] https://github.com/wildfly/wildfly/blob/8f620bbe6d481c9c2c6422e2250326a98... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-11255: ----------------------------------- Summary: EE Concurrency Utilities Managed Executors / Thread Pool runtime stats Key: WFLY-11255 URL: https://issues.jboss.org/browse/WFLY-11255 Project: WildFly Issue Type: Feature Request Components: EE Affects Versions: 14.0.0.Final Reporter: Brad Maxwell The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. {code} /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) { "outcome" => "success", "result" => { "context-service" => "default", "core-threads" => undefined, "hung-task-threshold" => 60000L, "jndi-name" => "java:jboss/ee/concurrency/executor/default", "keepalive-time" => 5000L, "long-running-tasks" => false, "max-threads" => undefined, "queue-length" => undefined, "reject-policy" => "ABORT", "thread-factory" => undefined } } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3193: ------------------------------------- [~tirelli] Thanks, good to know. Given that, then is the capability to order/reorder columns a compliment functionality? [~kkufova] Do we have that now, if not is there a jira for that? Likewise is there support for reordering rows? > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-400) Add Tests on Kiali Pyton Client

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-400?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-400: ------------------------------- Parent Issue: SWSQE-471 (was: SWSQE-399) > Add Tests on Kiali Pyton Client > ------------------------------- > > Key: SWSQE-400 > URL: https://issues.jboss.org/browse/SWSQE-400 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > Priority: Major > > Currently, there are no tests on Kiali Python Client. > I think we need add some tests there -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-473) Run Kiali Python Client Tests Via Jenkins Job

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-473: ---------------------------------- Summary: Run Kiali Python Client Tests Via Jenkins Job Key: SWSQE-473 URL: https://issues.jboss.org/browse/SWSQE-473 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Michael Foley Run tests via separate Jenkins job Run tests via PR trigger -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3193: --------------------------------------- [~uxdlc] as [~kkufova] said, it is common to add columns after the input of data in the table. In regards to the order of the columns, it is completely up to the user, as from a runtime perspective, there is no real difference. The user might prefer to keep columns of the same type side by side, or they might prefer to organize them in sets (e.g., Person1, Credit1, Loan1, Person2, Credit2, ...). > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-472) Prototype Kiali Python Client Test Case

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-472: ---------------------------------- Summary: Prototype Kiali Python Client Test Case Key: SWSQE-472 URL: https://issues.jboss.org/browse/SWSQE-472 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Michael Foley Create at least one test case to be used as a model for all tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-471) Tests on Kiali Pyton Client

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-471?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-471: ------------------------------- Sprint: Kiali Sprint #13 > Tests on Kiali Pyton Client > --------------------------- > > Key: SWSQE-471 > URL: https://issues.jboss.org/browse/SWSQE-471 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > > Currently there are no tests to validate that the Kiali Python Client is working properly with the Kiali REST API. The purpose of this Story is to get into place a set of tests that validate each of the supported Python Client API methods. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-471) Tests on Kiali Pyton Client

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-471: ---------------------------------- Summary: Tests on Kiali Pyton Client Key: SWSQE-471 URL: https://issues.jboss.org/browse/SWSQE-471 Project: Kiali QE Issue Type: Story Reporter: Matt Mahoney Assignee: Michael Foley Currently there are no tests to validate that the Kiali Python Client is working properly with the Kiali REST API. The purpose of this Story is to get into place a set of tests that validate each of the supported Python Client API methods. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-400) Add Tests on Kiali Pyton Client

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-400?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-400: ------------------------------- Team: (was: Infrastructure) > Add Tests on Kiali Pyton Client > ------------------------------- > > Key: SWSQE-400 > URL: https://issues.jboss.org/browse/SWSQE-400 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > Priority: Major > > Currently, there are no tests on Kiali Python Client. > I think we need add some tests there -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018