graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #02443
Re: [Question #193502]: Importing historical summed data gives weird aggregated result
Question #193502 on Graphite changed:
https://answers.launchpad.net/graphite/+question/193502
Status: Answered => Open
Jens Rantil is still having a problem:
Hi Michael,
Thank you SO much for this answer. I have two follow-up questions:
1) Would you like me to file a bug about the corner case? I am not
entirely sure what to write, but could put something together and refer
to this question. Are there are test cases for whisper that I could
update accordingly. I can't find any.
2) I'm seeing a problem with whisper if two events happen to happen at
the exact same second, or far back in time (second level of resolution).
Something that would be great as an addition to carbon would be to allow
"my.data +1 1334621057" and possibly
$ whisper-update.py test.wsp 1334621057:+1
. This would solve both of these issues and also make it way easier to
import old data to whisper/graphite (without writing custom aggreagation
script yourself). I am well aware of that this would require an
additional read for every write, but that would really only be a penalty
on that kind of incremental write (which would be optional). Just
curious, has this been discussed?
/Jens
--
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.