Question #193066 on Graphite changed:
https://answers.launchpad.net/graphite/+question/193066
Status: Open => Answered
Nicholas Leskiw proposed the following answer:
Is the timezone set in your Graphite configuration file? (local-
settings.py I think, maybe carbon.conf.)
Dmitry Molchanov <[email protected]> wrote:
>New question #193066 on Graphite:
>https://answers.launchpad.net/graphite/+question/193066
>
>Hello!
>We have a couple of metrics that store daily calculated values.
>At first look the problem looks like an problem of visualisation as we can
>see here (http://molchanov.pp.ru/savt.png).
>But further investigation shown that data sent to carbon-cache with correct
>local time (e.g. 12:00PM converted to unix timestamp).
>Timestamp is aligned to beginning of time interval of retention (00:00 GMT)
>when it is stored to database
>(whisper.py: myInterval = timestamp - (timestamp %
>archive['secondsPerPoint']) )
>Offset for our TZ (Europe/Moscow) is added when it is displayed, so data point
>is displayed at 04:00 instead of 12:00PM or 12:00AM at least.
>This makes a couple of problems with reading graphs and data manipulation. How
>should we handle it?
>
>
>--
>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
