[Feat Req]: Data source & dashboard limits on time range
currently there's a quick range of 5years back, but using the calendar picker and zoom out controls, you can go arbitrarily far back (e.g. 30 or 100 years even) however: - the tsdb may only have data up to a certain retention (a year, 3 months, ... ?) so it doesn't make sense to go back further - performance could degrade significantly or even tsdb crash if you go too far back. so i propose admin controls to: 1) limit how far back one can go 2) what the max time range is this would result in disabling of certain quick range options, restricting how far "zoom out" can go, and shielding users from certain timeranges in the calendar picker/editor. we could perhaps tie this in to the quota config system because available retentions can be dependent on which org you're in.
Posted by Dieterbe on Mar 8, 2016, 8:37 AM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
[Feat Req]: Data source & dashboard limits on time range
currently there's a quick range of 5years back, but using the calendar picker and zoom out controls, you can go arbitrarily far back (e.g. 30 or 100 years even) however: - the tsdb may only have data up to a certain retention (a year, 3 months, ... ?) so it doesn't make sense to go back further - performance could degrade significantly or even tsdb crash if you go too far back. so i propose admin controls to: 1) limit how far back one can go 2) what the max time range is this would result in disabling of certain quick range options, restricting how far "zoom out" can go, and shielding users from certain timeranges in the calendar picker/editor. we could perhaps tie this in to the quota config system because available retentions can be dependent on which org you're in.
Comments (0)
No comments yet. Start the discussion.