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:
Wait though..... I thought thats why carbon needed the time stamp? The
graphite page even somewhat advertises that as a feature for quickly
importing old data.

So I cant send data whenever I'd like as long as the time stamps match
up?

My understanding was the graphs would have a slight delay until the
remaining data got there but the order and delay didn't matter.

Am I confused or is this a bug of some sort? If data needs to come over
right away then why do I need the time? The receiving side should just stamp
the current time on it and store then?

That is less functional than what I was expecting. What are your thoughts? I
planned to gather data from machines like laptops not currently on the
corporate network and send it all once they reconnect filling in the gaps.
Sounds like that wont work now.

On Tue, Feb 9, 2010 at 3:03 AM, 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:
> So the problem is with the client script I believe. I ran it on my
> system and I saw that it was outputting metrics every 0.5 seconds (to my
> terminal) and also that my data had the same gaps as yours. Then I
> commented out the "print message" line near the bottom and saw that
> while every 0.5 seconds data is being collected, data is only sent once
> every 5 seconds (because of the transmit_delay setting), which explains
> the gaps in the graphs. If you set transmit_delay to 0.5 then the graphs
> are smooth.
>
> As for your CPU info graphs they did not load for me either, it is
> because of a javascript exception caused by the presence of the %
> character in your graph's title. I can add some code to search and
> replace user inputs' % with the proper escape sequence to avoid this
> issue in the future, but for now the quick fix is to just not use %.
>
> --
> 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=6
>
> 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.