Hi Martin,

I think this is how the default monitoring intervals have to be interpreted:

RRAs \
"RRA:AVERAGE:0.5:1:240"    \
"RRA:AVERAGE:0.5:24:240"   \
"RRA:AVERAGE:0.5:168:240"  \
"RRA:AVERAGE:0.5:672:240"  \
"RRA:AVERAGE:0.5:5760:370"

                                                             used for 
display of
Take 240 samples at        15 seconds                 intervals    hour
Take 240 samples at   24 × 15 seconds (= 6 minutes)   intervals    day
Take 240 samples at  168 × 15 seconds (= 42 minutes)  intervals    week
Take 240 samples at  672 × 15 seconds (= 168 minutes) intervals    month
Take 370 samples at 5760 × 15 seconds (= 24 hours)    intervals    year

So I think for your case you have to decide "how many" samples of the 
chosen sampling rate (20 minutes, 8 hours etc.) you want to collect 
which then determines the overall time interval covered by this specific 
sampling rate.

The main question is: How granular do you want the sampling rate to be 
for a given time interval?

This then determines:
a) the number of multiples of 15 seconds (to get the sampling rate)
b) the total number of samples required ("number of samples" x "sampling 
rate" = "time interval")

Hope that helps.....

Regards,
Michael

On 11/25/2009 02:24 PM, Martin Knoblauch wrote:
> Hi folks,
>
>   currently I am setting up monitoring for a cluster, where the demand is to 
> have additional monitoring intervalls. We want to see stuff like 
> "20-minutes", "8-hours", "2-weeks", "3-month" and "6-month". Doing so seems 
> easy, but I have a question on the RRA definitions.
>
>   The default setup seems to be (assuming a 15 second polling intervall):
>
> hour    ->  "RRA:AVERAGE:0.5:1:244"
> day     ->  "RRA:AVERAGE:0.5:24:244"
> week   ->  "RRA:AVERAGE:0.5:168:244"
> month ->  "RRA:AVERAGE:0.5:672:244" (more like 4-weeks :-)
> year    ->  "RRA:AVERAGE:0.5:5760:374" (367.86 days)
>
>
>   So from hour to month  we have 244 datapoints with nicely increasing steps 
> (1,24*1,7*24*1,4*7*24*1). So why are we doing it differently for the year? I 
> would have expected the "year" RRA to be "RRA:AVERAGE:0.5:8784:244" (366 
> days). Any particular reasons for this?
>
> Cheers
> Martin
> ------------------------------------------------------
> Martin Knoblauch
> email: k n o b i AT knobisoft DOT de
> www:   http://www.knobisoft.de
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Ganglia-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ganglia-developers
>
>    

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ganglia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to