-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timechart: support data-driven time range #52
Comments
Is the idea that we would no longer calculate _jut_time_bounds and send to the chart? |
If the user explicitly specified |
How will this play with -duration? Would we drop that parameter? |
Right now |
The interplay with
So if you specify Not sure what the time overlay mode would do, then; maybe |
+1 for this feature. |
Currently, the time range of a timechart is driven by the
-from/-to/-last
supplied to the juttle sources that eventually end up feeding points into it. The idea behind this that if you request a time range of 1 day but only have data for the middle 12 hours, we want to make it clear that there was no data for the first 6 hours and the last 6 hours.However, it is somewhat common to do a juttle query across a very wide time range because you have little upfront knowledge about where this data is located. In this case, you do want the chart to only show the data instead of days (or possibly years) of no data.
This is a proposal to add an option to timechart that will drive whether the time range should be determined by the range of the data or the range of
-from/-to/-last
.Proposed names:
cc @demmer @dmehra
The text was updated successfully, but these errors were encountered: