Andrew Dinn wrote:
Paul,
Why don't you use Byteman to log the info you need? This ought to be a lot cheaper than globally switching on trace for the transactions code. Also, you should be able to print more info than is printed by the trace code. If you develop a simple helper jar you could also direct the data to a known location rather than having to trawl through the log.
This was my original plan for getting this working. However, it's not compatible with the requirement that: "we should be able to parse the customer submitted logs attached to support cases". I'd need to speak to GSS about this, but we could change the requirement to: "The customer should be able to easily provide a dump of the transactions to attach to a support case".
Also, we were thinking that the logs should be complete. Therefore, all the information we gather should be present in the logs. If it isn't then we add it to the logs and then use it by the tool.
However, I take your point that the Byteman approach is likely to be more powerful and performant. It's definitely something we should consider.