graphite-dev team mailing list archive

[Nicholas Leskiw <nleskiw@xxxxxxxxx>]

A.) You're correct, priority is no longer used.  The rules are tested in order, and the first match is used.  Since everything_1min_1day matches anything, all metrics will use it.

B) the retention is in the following format: 

seconds_per_point:number_of_points_to_store

So 60 seconds = 1 minute, 1440 minutes = 1 day.

There's a new way to set these with min, h, d (minute hour day) suffixes as well.

-Nick

On Feb 22, 2011, at 4:22 PM, Kindjal <question146483@xxxxxxxxxxxxxxxxxxxxx> wrote:

> New question #146483 on Graphite:
> https://answers.launchpad.net/graphite/+question/146483
> 
> I couldn't figure out why my storage schema was not being used.  It appears that "priority" is completely unused.
> 
> # This is from .example.conf
> [everything_1min_1day]
> priority = 90 # I tried using 90 and 110
> pattern = .*
> retentions = 60:1440
> 
> # These are the schemas I want to actually use
> [foo]
> priority = 100
> pattern = ^foo\.
> retentions = 1800:8640
> 
> [bar]
> priority = 100
> pattern = ^bar\.
> retentions = 60:43200,900:350400
> 
> Neither foo nor bar were ever used.  Only the default.  Regardless of priority.  I grepped through the source and don't find "priority" used anywhere.  Am I missing something?
> 
> Also, in the above schemas, it looks like the default, which claims to save 24 hours of data, really only saves 24 minutes of data.  I wonder if there's a missing * 60 multiplier someplace.
> 
> 
> 
> -- 
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to     : graphite-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help   : https://help.launchpad.net/ListHelp