Johnathon Lee wrote:
From the GSS viewpoint, we sometimes have customers that are unwilling to explicilty turn Byteman on in production environments. This would need to be taken into consideration, but I like the flexibility that Byteman usage would be able to add as use cases come up and different rules may need to be modified/added.
Maybe a hybrid solution would work. We use logging for the stuff that is already logged and Byteman for things that are not logged in the target release. Byteman could then produce a log message for what it finds, which would then be parsed by the latest version of the profiler.
For example, we are (possibly) adding a new log message to Narayana 5.0.0.M4 which is needed by the profiler to construct an interposition hierarchy. This would mean that we can only use this on EAP versions with Narayana in (so not EAP 6.x). However, if we used Byteman to produce the log message, we could make it work with EAP 6 and prior.