Metrics - runtime statistics

[bytor99999]

Can the ManagedComponent be expanded to be able to gather runtime statistics on that component.

As examples for Connection Pools,
connectionCount
availableConnectionCount
maxConnectionsInUse
inUseConnectionCount

Queues and Topics
ConsumerCount
MessageCount

Thanks

Mark

[bytor99999]

When we were discussing the runtime statistics, I believe it was brought up that they would be returned as ManagedProperties. And we were going to look into our ability to be able to handle this approach.

Right now, I don't see an issue with this except how they are returned. If we request runtime statistics is the entire ManagedComponent returned with all of its properties, the configuration and runtime statistics, or would it return just the runtime statistics?

Mark

[bytor99999]

http://jira.jboss.com/jira/browse/JBAS-4394

[adrian.brock]

"bytor99999" wrote:
When we were discussing the runtime statistics, I believe it was brought up that they would be returned as ManagedProperties.

They'll be liked ManagedProperties, but you don't need all the support for changing
them :-)

e.g. psuedo code:

public interface ManagedObject
{
 // ...

 Map<ServerName, List<MetaValue>> getStatistics();
}

What is required is a way to refresh (re-retreive them from the server -
perhaps individually) and also being able to understand that the statistics are
available multiple times from the different servers in the cluster where the object is deployed.

Where they do look more like ManagedProperties is the ability to annotate
parts of them to explain how they should be used, e.g.
whether the statistic (or a component of the statistic)
is monotonic (always increasing) or random
or whether the it is an average, etc.

[bytor99999]

Just noticed on DataSource that there are no statistic managed properties defined.

There are on JMS Topics and Queues, which I should be able to test with.

But it would also be nice to have them for DataSources.

Thanks

[starksm64]

Ok, we'll get some stats in for beta4.
http://jira.jboss.com/jira/browse/JBAS-5179

[starksm64]

This has been fixed in trunk.