Change one-minute precision assumptions in UI
Bug #249529 reported by
chrismd
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Graphite |
Won't Fix
|
Low
|
chrismd |
Bug Description
The auto-refresh button in the Browser UI and the redraw command in the CLI both assume minutes as the unit of time. Several users use sub-minute precision, so we at least need the option of doing sub-minute refreshing.
Changed in graphite: | |
assignee: | nobody → chrismd |
Changed in graphite: | |
status: | In Progress → Triaged |
Changed in graphite: | |
status: | Triaged → Confirmed |
Changed in graphite: | |
importance: | Undecided → Low |
milestone: | none → 0.10.0 |
Changed in graphite: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
One step closer to implementing an auto-refresh that is based on the lowest- common- denominator for the current metrics' precision. I've implemented per-metric context data persistence that I will use in in the future to determine the refresh rate.