The following quote is from the SI reference manual:
While I can see that this is true for managing the components (using the control bus), what about monitoring a SI application using SI as the messaging system for the monitoring messages?As described in (EIP), the idea behind the Control Bus is that the same messaging system can be used for monitoring and managing the components within the framework as is used for "application-level" messaging.
I was thinking to do something like this:
I have some sort of simple GUI application for displaying monitoring info, including historical data. This application reads its data from a database. I would like to fill this database using SI, by exposing the components as MBeans using a <jmx:mbean-exporter>, and then periodically read all the attributes using <jmx:attribute-polling-channel-adapter> and storing them using <jdbc:outbound-channel-adapter> (so the monitoring application can show nice graphs). However, as far as I can tell, this would require one <jmx:attribute-polling-channel-adapter> for each exposed attribute of each SI component, which will result in a huge amount of JMX channel adapters.
Is there another/better way to do this?