Graphite DurationUnit has confusing semantics

[pteichman]

I'm attempting to report timers to Graphite using millisecond units. With DurationUnit: time.Nanosecond (the default), they're off by a factor of a million. With DurationUnit: time.Millisecond, they're off by a trillion.

Is this a problem of documentation (there aren't any DurationUnit examples) or should all the timer metrics be t.Foo()/du rather than du*t.Foo()? I'm happy to make the patch in either case.

[pteichman]

I worked around this by compressing time in my calls to Timer.Update, e.g. DurationUnit: time.Nanosecond and:

-               stats.MsgTimer.Update(time.Since(start))
+               stats.MsgTimer.Update(time.Since(start) / time.Millisecond)

Am I misunderstanding the point of DurationUnit? I'm finding it hard to imagine a scenario when you'd need to log nanoseconds as a larger magnitude, which is the only option with the current code.

[rcrowley]

Looks like a bug, thanks.