Thanks. You raise a good point, and we need to change the webpage to clarify it. You don't have to put monitoring points in your processes, this is just one way that you can instrument in flight processes. In short there are four different routes, and the choice is up to you: 1. Publish events from the underlying message transport (JMS or whatever) to SeeWhy. You need to put XML events onto the SeeWhy JMS queue. This can obviously be done with or without a BPM tool being present. 2. Put monitoring points into your processes to put XML events onto the SeeWhy JMS queue (as above). 3. Use the SeeWhy JDBC adapter which can poll a database and create events 4. Use third party software or applicances (such as Goldengate for Databases, Covelight for IP traffic, CastIron etc) to stream events to SeeWhy SeeWhy is an event driven product which has the capacity to analyze vast quantities of data in real time, and to initiate actions in BPM tools as a result of the analysis. There are clear advantages from going against a stream, rather than a log file, but we are open to the best way to do it specifically in the context of the jBPM integration. There may be a few situations where you want to monitor every node, but the process state data cannot be derived from an underlying event stream. In these cases you either have to go against the log file or you'll need to put a monitoring point into the process. This is exactly the type of debate I was hoping we'd kick off. If there's universal demand for a log file based approach then we can look at tighter integration in more detail. I look forward to your any additional thoughts. Charles View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995291#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...