My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 141: Implement bucket-related statistics
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by sergio.b...@gmail.com, Dec 15, 2010
Other than the already implemented cluster statistics, it would be very useful to have some bucket-related statistics.
Here are a few useful data I'd like to see (per bucket):
* Number of documents locally hosted.
* Total number of documents.
* Number of writes.
* Number of reads.
Dec 16, 2010
Project Member #1 sergio.b...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Dec 16, 2010
Project Member #2 johansso...@gmail.com
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.
Dec 16, 2010
#3 you...@gmail.com
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.
Dec 16, 2010
Project Member #4 sergio.b...@gmail.com
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.
Dec 16, 2010
Project Member #5 johansso...@gmail.com
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
Dec 16, 2010
Project Member #6 sergio.b...@gmail.com
Absolutey agreed.
Dec 16, 2010
#7 you...@gmail.com
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.
Sign in to add a comment

Powered by Google Project Hosting