camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Preben.Asmussen" <p...@dr.dk>
Subject Re: Proof of concept for Camel Web Interface
Date Wed, 15 Aug 2012 16:06:44 GMT
Hi Lars

I had a look at Jolokia last year and was impressed by it's usability for
exposing jmx using http. Basically I wanted to use the Camel stats. for
monitoring purposes for our custom monitoring system.

At the end I found that the jmx stats wasn't enough to give you a reliable
picture of the health of a Camel integration. Something is missing eg. the
ability to check if a given resource being consumed by camel eg. a db, ftp
or file is working. Camel will only give you statistics (failure, completed
asf. ) when an exchange is being processed, and not if for example a db is
down (using the jpa consumer here).

At the end I developed a small monitoring capability for Camel that exposes
a rest interface for all our routes deployed. This monitor internally uses
the jmx stats to see if there has been any activity on the route within a
configurable interval of MS. If any activity it will use the stats to
determine if the route should report it's health as OK, WARN or ERROR. 
If no activity has been on the route it will run a Secondary target, meaning
a custom monitoring component that will check the consumer's endpoint. These
secondary targets are eg. a db, file, ftp resources with the purpose to
checks if the resource is available and in good state (reporting the same
stats as above).
When the integration is deployed as a war each Camel context has it's own
monitor.xml where monitoring rules are set up for the integration, exposing
a rest interface for that component.

The only thing needed now is a integration monitor that knows each component
(Camel context/war) deployed and it's rest endpoint. The integration monitor
runs in intervals and collects stats from each component, builds a
correlated view of the hole platform's health and exposes that as a rest
endpoint. 
This can then be consumed by in our case HP Openview to report on platform
health. Besides that a gui is available.

Preben

   



--
View this message in context: http://camel.465427.n5.nabble.com/Proof-of-concept-for-Camel-Web-Interface-tp5717349p5717409.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message