How to graph one data point per hour?

Can you please run /usr/local/bin/whisper-info.py on one of the files and
post the result?

2012/2/23 François Beausoleil <email address hidden>

> New question #188637 on Graphite:
> https://answers.launchpad.net/graphite/+question/188637
>
> I generate summaries hourly. I want to graph how long the generation took.
> Works just fine using "Keep last value", but only if I keep the graph's
> width / time interval to 24 hours of less. More time than that and the
> values disappear. I'd like to graph the time it takes to generate my
> summaries over a period of a month, maybe a bit more.
>
> My storage-schemas.conf for the metric is (using revno 551, whatever
> version that is):
>
> [summaries]
> priority = 100
> pattern = ^summaries
> retentions = 1h:30d
>
> According to the docs, this is intended to mean that I get 1 data point
> per hour, and I want to keep 30 * 24 data points around. What am I missing?
>
> Thanks!
> François
>
> --
> 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 : <email address hidden>
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help : https://help.launchpad.net/ListHelp
>

Needs information

Here's the required information:

maxRetention: 2592000
xFilesFactor: 0.5
aggregationMethod: average
fileSize: 259252

Archive 0
retention: 86400
secondsPerPoint: 10
points: 8640
size: 103680
offset: 52

Archive 1
retention: 604800
secondsPerPoint: 60
points: 10080
size: 120960
offset: 103732

Archive 2
retention: 2592000
secondsPerPoint: 900
points: 2880
size: 34560
offset: 224692

Oh, I see: the file was created before I put my summary in place. Can I run whisper-resize concurrently with carbon writing? I suspect I'll have to stop carbon (or use a new metric) before I can change that.

Thanks!

You can run whisper-resize while carbon is running...it makes a backup before operating on the file.

This should also eliminate the need for keepLastValue and also save you a lot of disk space.

-Nick

On Feb 23, 2012, at 1:40 PM, François Beausoleil<email address hidden> wrote:

> Question #188637 on Graphite changed:
> https://answers.launchpad.net/graphite/+question/188637
>
> Status: Open => Solved
>
> François Beausoleil confirmed that the question is solved:
> Oh, I see: the file was created before I put my summary in place. Can I
> run whisper-resize concurrently with carbon writing? I suspect I'll have
> to stop carbon (or use a new metric) before I can change that.
>
> Thanks!
>
> --
> 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 : <email address hidden>
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help : https://help.launchpad.net/ListHelp