Skip to content
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

Override of 'now' for systems with lagged data feeds #3419

Closed
boutcher opened this issue Mar 23, 2015 · 2 comments
Closed

Override of 'now' for systems with lagged data feeds #3419

boutcher opened this issue Mar 23, 2015 · 2 comments

Comments

@boutcher
Copy link

For systems that load data in batches (let's say, every 5 minutes), it's useful to have the concept/selector for 'now' to be now-Xminutes.

This way, there won't be a drop to 0 of all charts and graphs that are up to current time.

I'm not sure at what level this should be configured... Index level?

@rashidkpc
Copy link
Contributor

You would definitely want this on the index level. This would require the date math parser to have knowledge of the index pattern which it doesn't currently. What happens if 2 indices on the same dashboard have different offsets? What do you put on the right edge of the chart? Is it the actual "now"? Each individual index's offset "now"? The latter would mean you've have 2 bars in the same place that actually reference different times.

I can see the use here. There's a lot of edge cases that would need to be explored to make this feasible.

@tbragin
Copy link
Contributor

tbragin commented Jan 5, 2017

Looks like there is another ticket related to the same ask with more discussion, so i will move comments there and close this as a dup:
#2394

@tbragin tbragin closed this as completed Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants