Metrics with a step greater than one hour are displayed at incorrect times in non-UTC timezones
Bug #989423 reported by
Michael Leinartas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Graphite |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Timestamps fed into Whisper are rounded back to the nearest factor of the archive resolution, creating a predictable 'bucket' for which a single value can be stored. At archive resolutions over 1 hour, the beginning of this bucket is only correct if the graph is displayed in UTC. Timezone differences will shift the bucket.
From whisper.py: myInterval = timestamp - (timestamp % archive[
For example, for a 1 point daily resolution the beginning of the displayed daily point is expected at 00:00 local time. However, it is stored in UTC as 00:00 and thus will be displayed at the localtime's offset from 00:00 UTC (e.g. 4am for a UTC+4 timezone).
| Changed in graphite: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Michael Leinartas (mleinartas) wrote | #1 |
| Changed in graphite: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Migrated to Github: https:/