[General] Technical information of component for monitoring
rnaudin
roland.naudin at petalslink.com
Wed Mar 16 10:21:38 CET 2011
Hi all,
We will propose an Admin operation to get technical information about component/SA/SU, in order to audit/alert... with any admin client.
For the statistic data, it will be a push/pull mechanism. The data are proposed periodically by the component/SU, in a 'window'.
The admin operation retrieve the last 'windowed' ones.
The window can be reconfigured at runtime by a component runtime parameter.
I propose this thread to collect the informations that seam relevant to expose.
I have identified common data:
-last start/stop/shutdown (component/SA/SU)
-number of messages processed since last recovery (component/SU)
-number of messages in fault/error since last recovery (component/SU)
-number of messages processed since last window (component/SU)
-number of messages in fault/error since last window (component/SU)
Some interesting statistics:
-ratio of the static part of the processor thread pool (the borrow time against the idle time for all the threads) since last window
-number of threads of the dynamic part of the processor thread pool used since last window
specific data can be exposed by component:
-number of connection failure by BCs (since there a retry policy, the messages in fault/error are not enough)
-number of BPEL instance eg for BPEL...
others ideas?
-------------------- m2f --------------------
Subscribe/Unsubscribe emails notifications :
http://forum.petalslink.com/m2f_usercp.php
Response to this email will be posted on the Petals forum.
Please delete the existing text before responding :)
Read the topic online:
http://forum.petalslink.com/viewtopic.php?p=31502#31502
-------------------- m2f --------------------
More information about the General
mailing list