Question #155811 on Graphite changed: https://answers.launchpad.net/graphite/+question/155811
Nicholas Leskiw proposed the following answer: Clarification: this draws null as zero on screen. The underlying data is unchanged. You can still roll the data up however you see fit. Also, for some data, it's important to know *when* an event occurred - information that would be lost if using a lower precision. -Nick On Tue, May 3, 2011 at 7:53 PM, Jason Dixon <[email protected]> wrote: > Question #155811 on Graphite changed: > https://answers.launchpad.net/graphite/+question/155811 > > Jason Dixon posted a new comment: > I would just like to add a philosophical comment that replacing nulls > with zeros is a bad precedent. It skews your data, particularly when it > gets rolled up further down the line. I think a better approach would be > to tweak your minimum precision to a range where you know you'll get at > least one datapoint. > > -- > 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 > -- 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
