You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Lev Kozakov <le...@gmail.com> on 2008/02/15 00:19:48 UTC

UIMA-AS client side JMX stats

I would like to use UIMA-AS client side JMX stats for monitoring
performance of a client application, which is connected to a UIMA-AS
service queue. To provide flexible dynamic monitoring capabilities, I
would like to report several performance parameters, including the
following:
(1) average parameter values per hour/day since the last refresh;
(2) max parameter values for the last hour/day.

To be able to calculate (1), I just need to get the last refresh time,
so my 1st suggestion is adding 'LastRefreshTime' to the client side
JMX stats.

Calculating (2) is, of course, more complicated task. My suggestion
here would be to have 2 different sets of max parameters:
'AbsoluteMax...Time' (since the last general refresh) and
'LatestMax...Time' (since the last partial 'max' stats refresh). To
provide the 'LatestMax...Time', we need to enable partial refresh of
'max' stats without refreshing other stats. And, of course, together
with the 'LatestMax...Time' parameters we'll need to add also
'LastMaxRefreshTime' parameter to save the last refresh time of
'LatestMax...Time' parameters.

In addition to this, I need to be able to report the average/max
client response latency time. If I take the sum of
'AverageSerializationTime' + 'AverageTimeToProcessCas' +
'AverageSerializationTime', it still does not include everything I
need, e.g. transportation/queueing time. Is it possible to add
'ResponseTime' parameters, like 'AverageResponseTime',
'MaxResponseTime', 'TotalResponseTime', to report full time of
processing client requests?

Thanks,
-- Lev

Re: UIMA-AS client side JMX stats

Posted by Jaroslaw Cwiklik <ui...@gmail.com>.
I consider the above an application specific functionality which can be
implemented using current code.
The UIMA-AS client notifies the application every time a reply from a
service is received. The application
receives a callback that includes a CAS and statistics associated with the
CAS. The application can
choose to aggregate stats in a different (app specific way) using generic
stats provided. UIMA-AS JMX stats
are meant to provide generic information about the running system and I dont
think that the change is
needed. Application *may* decide to create its own specialized MBeans and
populate them from the
application callbacks.