Open GoogleCodeExporter opened 9 years ago
Original comment by sergio.b...@gmail.com
on 16 Dec 2010 at 9:43
We should give some thought to what more to expose, especially for
metrics/monitoring.
I'd think that operations staff wouldn't mind being able to poll for data for
Cacti-graphing (or for other tools).
So some sort of breakdown with averages over time, reads/writes per minute(or
other time intervals) would be a nice-to-have.
Original comment by johansso...@gmail.com
on 16 Dec 2010 at 10:42
It's a good idea add metrics data to the rest interface so that, for example,
TerrastoreConsole will be able to show this real time info.
Original comment by you...@gmail.com
on 16 Dec 2010 at 1:23
Time-based metrics are usually computed by such a tools by simply extracting
and combining data at different points in time: so I think we shouldn't provide
time-based data by ourselves.
Original comment by sergio.b...@gmail.com
on 16 Dec 2010 at 3:08
Right, if that is the case then we don't have to do it specifically.
I guess my main underlying point is that the nice-to-have is that the
statistics we do provide accomodate monitoring tools in a good way, in addition
to custom/manual interpretation & the Terrastore Console
Original comment by johansso...@gmail.com
on 16 Dec 2010 at 3:13
Absolutey agreed.
Original comment by sergio.b...@gmail.com
on 16 Dec 2010 at 3:15
Sergio, I think it should be a Terrastore behavior, I cannot think how do it
otherwise in Terrastore scenario without compromising realtime aspect.
In Camel, for example, there're some useful stats accessible by jmx, as message
flushed/mins, max process time ecc..
I think these stats are calculated in real time by Camel, maybe I didn't
understand what you mean.
Original comment by you...@gmail.com
on 16 Dec 2010 at 4:12
Original issue reported on code.google.com by
sergio.b...@gmail.com
on 15 Dec 2010 at 2:44