You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by bebop01 <ma...@pleus.net> on 2006/12/05 11:42:43 UTC

Tracking and Audit

Hi,

I would like to implement a tracking system that allows to track the
following data:

- Status of the executed components (success, failure) with error message in
case of failure
- Start and stop time for each component
- Endpoint configuration at the time of execution (ftp url, username, etc.)
- Messages that were received and sent by the components

Based on the tracking data it should be possible to analyse the the entire
process end-to-end.
The tracking data should serve as the basis for health and business activity
monitoring.

I've had a look at the audit features in servicemix. It seems to be focused
on the message exchange and not on the components.

My main issues are:

1. Endpoint configuration
I did not find a way to gather the runtime configuration for the endpoints
in the auditor. It's not enough just to save the exception. The admin should
have a way to see the configuration at the time of execution, which might be
different from the configuration in the deployed serviceassemblies.

2. No data under certain circumstances
If I use a binding component (e.g. FTP) and that component fails, I don't
see anything on the auditor and therefore nothing is tracked. So for the
admin everything looks fine, but actually a problem occured. Therefore it
seems that it's not possible to build a health monitoring system based on
the audit functionality.

It there another way to hook up a custom listener in order to get more
detailed information about the executed components?

Any suggestions on how to implement a reliable tracking system would be
highly appreciated.

-- 
View this message in context: http://www.nabble.com/Tracking-and-Audit-tf2760713s12049.html#a7697050
Sent from the ServiceMix - User mailing list archive at Nabble.com.