graphite-dev team mailing list archive

[AcidTonic <question99926@xxxxxxxxxxxxxxxxxxxxx>]

Question #99926 on Graphite changed:
https://answers.launchpad.net/graphite/+question/99926

    Status: Answered => Open

AcidTonic is still having a problem:
Thanks for the support advice...

I rant the following command to double check I deleted everything when
making the schema change.

whisper-info.py storage/whisper/system/cpu_util_percent.wsp
maxRetention: 315360000
lastUpdate: 1264983378
xFilesFactor: 0.5
fileSize: 5760052

Archive 0
retention: 172800
secondsPerPoint: 2
points: 86400
size: 1036800
offset: 52

Archive 1
retention: 2592000
secondsPerPoint: 60
points: 43200
size: 518400
offset: 1036852

Archive 2
retention: 315360000
secondsPerPoint: 900
points: 350400
size: 4204800
offset: 1555252

So I really only want 2 second precision but I'm gathering every .5 to
really make sure I'm getting data there quick enough. The script truly is
sending data fast enough, any ideas?

I actually hit another bug trying to save graphs with cpu information. They
wont show up like my other graphs  that I've saved. I can open a separate
issue if you'd like.

For now I've exposed my graphite page to the net so you can fiddle with it.
It's not production so I really  dont care about the data.... Just dont
delete any other graphs I've saved and feel free to build your own for
testing.

My graphite url.... http://216.150.226.11:81/

Cheers,

On Mon, Feb 8, 2010 at 4:08 PM, chrismd <question99926@xxxxxxxxxxxxxxxxxxxxx
> wrote:

> Your question #99926 on Graphite changed:
> https://answers.launchpad.net/graphite/+question/99926
>
>     Status: Open => Answered
>
> chrismd proposed the following answer:
> Interesting... the output of the whisper-fetch command shows that the
> data is being stored in 1-minute intervals so maybe your intended
> storage configuration was not in effect when the wsp file was created.
> You can run whisper-info.py on the same wsp file to verify. Then again
> it could just be that a lower precision archive covered the time range
> you queried.
>
> Basically the approach I would take in debugging this is as follows:
>
> First log the output of your script for a period of time to see what data
> it is sending.
> Then run whisper-fetch on the wsp file to see what data was being actually
> stored for that period of time (you should specify the time range
> explicitly). I would recommend doing this in as close to realtime as
> possible to ensure only the highest precision archive in the database is
> involved.
>
> Your script looks like it should work, collecting data every half a
> second, and sending everything every 5 seconds. Since your archive is
> only configured with 2-second precision you will only be actually
> storing 1/4th of your data points.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/graphite/+question/99926/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/graphite/+question/99926
>
> You received this question notification because you are a direct
> subscriber of the question.
>

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.