Add monitoring support for dispatchers

[reactor]

Add monitoring support for dispatchers

[pasviegas]

I think most of the frameworks lack in a good way of metering and monitoring.

It would be nice to have something like metrics (http://metrics.codahale.com), so one could easily have the control over the app by annotating the consumers, etc.

[smaldini]

Interesting suggestion. I think we need a lightweight permanent monitoring
mech and a optional statistics system, enabled through a configuration
(annotation/builder/properties). I'll look into metrics in depths.

On Thu, May 16, 2013 at 1:15 PM, Pedro Antonio Souza Viegas <
[email protected]> wrote:

I think most of the frameworks lack in a good way of metering and
monitoring.

It would be nice to have something like metrics (
http://metrics.codahale.com), so one could easily have the control over
the app by annotating the consumers, etc.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-17997411
.

Stéphane

[pasviegas]

Yes, thats what I am talking about! :D
An optional statistics system would be really nice!
I don't know if it is as lightweight as you want, but I hope you like the concepts of metrics.

The framework Dropwizard (https://github.com/codahale/dropwizard) uses it. It exposes default metrics and you can add more if you want.

[smaldini]

DropWizard is a good example, thanks for pointing that :)
Be sure that is on the top priority, the list of asynchronous libraries without proper monitoring is unfortunately too big - we don't want to repeat the same mistake.

[markpollack]

We are working quite heavily on metric/analytics in SpringXD, check the
repo. That is where we should drive requirements for features etc. can
sync up more later.

[smaldini]

experimental contract and UI will be available from 2.5.0.M1 and we will iterate on polishing it in new issues.