Indika
The purpose here is to be able to quickly enable message tracing at
different levels, and then have the capability to monitor messages -
possibly from elsewhere. For example one may want to enable tracing of
messages which goes through a particular proxy service, and monitor
these through chainsaw. We also need to support a clustered environment
here, so that one could separate the trace messages per server etc.
asankha
indika kumara wrote:
hi all
It is valuable if the tracing capability can be added to each of the
mediator,endpoint and proxy service, Then it is flexible to trace
specific information which local to a particular mediator. So i
suggests to add a optional attribute " trace="Value"(where "Value "
should be "enable" or "disable") to each of mediator,endpoint and
proxy service. If a mediator does not has this attribute, then the
attribute value should be inherited from the parent mediator.
Ex: <send trace="disable" />
The trace information need to be separate from the log information and
it should be gone to a separate destination(file,memory,etc..).
I will crate a jira for this and will upload patches for all of these
features.
Please give your comments on this...
Thanks
Best Regards
Indika
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
