[switchyard-issues] [JBoss JIRA] (SWITCHYARD-647) Service metrics

[Gary Brown (JIRA)]

Gary Brown created SWITCHYARD-647:
-------------------------------------

             Summary: Service metrics
                 Key: SWITCHYARD-647
                 URL: https://issues.jboss.org/browse/SWITCHYARD-647
             Project: SwitchYard
          Issue Type: Feature Request
            Reporter: Gary Brown


Will describe some of the features that are required in this area, but after discussion should probably be created as separate sub-tasks.

a) Service managed objects

Need to have an internal managed object structure for the switchyard service application representing the components of interest. Initially I think from a management/governance perspective, only the public provided/consumed interfaces are relevant, even though there may be multiple internal components that interact to implement the service - but that can be discussed.

Suggestion would be to have a hierarchy with the service containing both the provided and consumed interfaces, with each interface further containing its operations.

For each operation it should be possible to record invocation stats (e.g. number of invocations and min/avg/max response times) for both normal responses, aswell as fault responses - having the stats broken down per fault type.

It may also be useful to record stats against invocations that fail for technical reasons, e.g. communications failure or security.

b) RESTful service to provide access to the service managed object information

c) Optionally a JMX interface, to enable management products to access the information

d) RHQ/JON agent plugin, to periodically collect the service metric information, as well as providing auto-discovery capabilities for services, so that a user does not have to manually configure services into JON

e) The final aspect of this task would be to enable developers to define 'event hooks' upon which they can provide additional adhoc governance requirements - however this requirement is probably satisfied by the handler mechanism? Although possible we may wish to provide out of the box handlers geared to this task, possibly with a logging variation (and others??).



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira