Guillaume Nodet <[email protected]> wrote on 09/30/2010 11:54:57 AM: > Has anyone thought about doing that yet? The interceptors on the beans > could easily be used to monitor service calls and expose some statistics > about those (time to complete an invocation, invocations p/second, etc...) > I haven't given that much thoughts yet, but it sounds a good idea at first > glance.
Months ago I prototyped something a bit similar for visualizing service calls in GOAT, but never got around to hooking my back end up to the GOAT front end. The idea would be that not only would GOAT show you a dynamic view of your architecture, it could even give you a dynamic view of the control flow, by - for example - flashing the service wiring triangle between two bundles each time a service was invoked. With the benefit of hindsight, using the blueprint interceptors would have been a much better implementation, of course. I do think there's value in exposing this kind of monitoring information, and I think if we do it we should also consider wiring it into GOAT at the same time. It would look *incredibly* cool when we show Aries to people, and that kind of visualization is also a useful diagnostic tool for users. (Thinking aloud, GOAT would also be a useful mechanism for surfacing the aggregated statistics - if you hovered over a service triangle, we could bring up a pop up with the invocations per second and average time and so on. I guess we'd want to investigate the performance impact of collecting this sort of information and make sure any design also has a 'zero-overhead' option. Holly Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
