I developed a custom monitoring solution where that uses route jmx stats. to report the health of a route by looking af completed and failed exchanges. The solution is generalized, so that you can configure which routes should be monitored by route name. Route stats. are not always enough though since this requires that there has been an exchange. Typically som Camel consumers like file/ftp jpa asf. doesn't create an exchange if there has been an io error connecting to eg. ftp/file or a db is down. For that reason I have developed some custom resource monitors eg. db, file, ftp monitors that can be connected to each route monitor as a secondary target so that if there has been no exchanges within a given timespan the secondary target is run to check an external ressource.
The monitor config gets deployed with the camel app. as a war and exposes a rest interface with a overall health status of the app. For a global overview of all integrations running there is a integration monitor that knows each rest endpoint, calls each one, and correlates this to a global health state of all deployed camel apps. The global healthstate is exposed as a rest interface that gets called by HP Openview. A GUI is also available. I haven't put it at github, mostly because of lack of time. Atm I'm working on a bam solution where throughput, total number of messages, total message size can be monitored over time. For that I'm using WSO2 bam - www.wso2.org. Looks really cool :-) Source is available at https://github.com/pax95/bam-toolbox if you wanna have a look, but it's still work in progress. Best Preben -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Monitoring-Tool-tp5618301p5723124.html Sent from the Camel - Users mailing list archive at Nabble.com.
