-
1. Re: Monitoring
The current MR2 release has no explicit support for monitoring. However, that is an area where we will be concentrating effort between now and the GA release.
What are your requirements? -
2. Re: Monitoring
Hi Mark,
well, some of the basic stuff would be an infrstructure for real-time
logging of events happening in the bus for analysing, tracking and
auditing. Some of events would be : call of services, chaining of actions,
publish/subscribe events, application flow, notifications, and some
advanced stuff like tracking of QoS, etc...An event should
be defined in a useful and meaninful format.
Regards -
3. Re: Monitoring
Do you need specifics on service instances and locations in the notifications?
Are you assuming you would get events and than store them on your side within a global monitoring system?
Do you want alerts based on thresholds associated with invocations, timing, etc...? Pseudo rule based alarming?
Are you using this information to potentially bill/invoice clients or services of a bus? -
4. Re: Monitoring
"Spike_S" wrote:
Hi Mark,
well, some of the basic stuff would be an infrstructure for real-time
logging of events happening in the bus for analysing, tracking and
auditing. Some of events would be : call of services, chaining of actions,
publish/subscribe events, application flow, notifications, and some
advanced stuff like tracking of QoS, etc...An event should
be defined in a useful and meaninful format.
Regards
Coincidentally this topic has been high on our agenda at JavaOne. A lot of what you've mentioned above may appear in the GA release due in the next few months. -
5. Re: Monitoring
You might check out the MessageStore feature as well. It can be used declaratively to "wiretap" messages to a database as well as push the messages on to its original destination.
Unfortuantely we don't have a quickstart that illustrates this capability of JBossESB at this time. It is is on my ToDo list. :-)
Burr