Keith Babo <kbabo> updated the status of jira SWITCHYARD-1694 to Resolved

Keith Babo <kbabo> made a comment on jira SWITCHYARD-1694

pushed

ER6 - the metrics are zero

Try bpm-service QS and call from CLI

[standalone@localhost:9999 subsystem=switchyard] :show-metrics(service-name="{urn:switchyard-quickstart:bpm-service:1.0}Shipping", type="*")
{
    "outcome" => "success",
    "result" => [{
        "name" => "{urn:switchyard-quickstart:bpm-service:1.0}Shipping",
        "application" => "{urn:switchyard-quickstart:bpm-service:1.0}osdemo",
        "successCount" => 0,
        "faultCount" => 0,
        "totalCount" => 0,
        "averageTime" => big decimal 0.0,
        "minTime" => 0,
        "maxTime" => 0,
        "totalTime" => 0L,
        "operations" => [{
            "name" => "ship",
            "successCount" => 0,
            "faultCount" => 0,
            "totalCount" => 0,
            "averageTime" => big decimal 0.0,
            "minTime" => 0,
            "maxTime" => 0,
            "totalTime" => 0L
        }],
        "references" => undefined
    }]
}

Rob - can you have a look at this?

It appears the metrics do not appear when using the wildcard, but you can get them by setting type="componentService"

Sorry, my previous comment is invalid.  The behavior is the same whether using * or componentService.  The data returned is invalid.

Metrics are only gathered for composite services, not for component services.

Metrics for composite services are aggregated on the component service, which they promote.  This means that if a component service is promoted twice, and a single message is sent through each composite service, the metrics for each composite service will show two messages being processed (because they metrics are tracked on the component service).

Metrics are gathered for component references, but these do not filter down to the actual component service/composite reference being invoked (well, maybe in the case of a composite reference).

To summarize, the issue is that we are not collecting metrics for component services that are not promoted.  And, if a component service is promoted more than once, the metrics may not be accurate for the composite services promoting it.

Rob Cernich <rcernich> updated the status of jira SWITCHYARD-1694 to Reopened

Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1694

Need to rework how metrics are aggregated/calculated.

There is an existing PR for this, it should be updated and tested.

Should also consider updating the JON plugin to retrieve this information.

For Fuse 6.2.1, we are moving to tracking all issues in JIRA.    Logged https://issues.jboss.org/browse/ENTESB-3621 to track this issue.

Closing - updates should go in the ENTESB JIRA logged.

Tom Cunningham <tcunning> updated the status of jira ENTESB-3621 to Resolved

Stefan Veres <sveres> updated the status of jira ENTESB-3621 to Closed