Hi, I am working on porting some mediation processes from a different ESB into Talend ESB. I need to be able to alert on the following type of events: Fault - a route exited with a fault. Missed Trigger - a route was not triggered as expected. e.g. a route should run once every 5 minutes but it has been > 5 minutes since last time it ran. Missed Consumer - a route started but did not finish within a configured amount of time. The 'Fault' condition seems pretty straight forward to monitor, but I'm not sure about Missed Trigger and Missed Consumer. A few complications here are 1) We will be running in a distributed environment, where a route may run on any one of 4 servers and 2) we need to be able to detect Missed Trigger and Missed Consumer even if the server that normally should run the route is completely offline and inaccessible. For example, if a route starts execution on a server and during execution the server completely dies, I need to be able to detect that the route did not finish, even if the server that was executing the route will never be online again (meaning, I can't look at logs for this purpose or depend on anything on the server to help me). We currently accomplish this using a separate (home grown) monitoring system that watches for process started and process ended events from the existing ESB, and it has logic to correlate things together based on message ids and correlation ids, and with that information it can determine if things have not finished or haven't been kicked off in X amount of time, etc. Our monitoring system listens on JMS because the existing ESB is tightly bound to JMS... each process has entry and exit topics, so it is a really straight forward thing to have a monitoring system watch entry and exit topics to see traffic happening on the ESB. Any ideas how we might accomplish this in Talend/Camel? In theory, we could put wiretaps in all the routes, and send messages to JMS, but I'm wondering if there is some more elegant way that does not require configuring wiretaps and jms clients in all the mediation routes. For example, possibly some camel context level events we can configure and listen to (preferably still over JMS). Thoughts/ideas?
... View more