Question #148743 on Graphite changed: https://answers.launchpad.net/graphite/+question/148743
magec posted a new comment: I think, the summarize approach is not enough. Now I'm experiencing another issue and I think there whould be no way of solving it. When carbon writes the points into whisper it uses the timestamp just to know what "metric slot" the data should be stored into and, as far as I know, the timestamp is then discarded. If a proper derivative function is to be implemented it should have into account the time interval between every two points. The summarize approach will still have this problem. My question is: Is the timestamp discarded as I say? There is another backend to store data, Does it discard the timestamp information as well? Whouldn't it be possible to store an offset for every point in the whisper file with the "drift" of the metric so a better derivative function can be implemented? I think this issue should be well resolved cause this case is so common, counters in network appliances, cpu, memory, etc... -- 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 protected] Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
