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

Rethink time selector, in particular the "All" option #313

Open
jasonish opened this issue Jun 9, 2024 · 0 comments
Open

Rethink time selector, in particular the "All" option #313

jasonish opened this issue Jun 9, 2024 · 0 comments

Comments

@jasonish
Copy link
Owner

jasonish commented Jun 9, 2024

Using all is nice while your database is small, but on a load instance, even 24 hours can put excessive strain on a system causing very long, uncancellable query times. Perhaps there is a reason Kibana and other tools default to 15 minutes.

This can be especially bad on SQLite installs.

Some ideas:

  • for inbox and alert views, implement a timeout and make it clear the timeout expired - the user can deal with the alerts and refresh - this could eliminate the time selector on the inbox completely which could be nice.
  • force time boxed views in alert/inbox views. For example, last 24 hours then an easy ability to step through 24 hour intervals
  • timeouts are not ideal for the report pages as difference data points on the same page won't cover the same time period, in this case forcing time boxing might be better.

I don't think there is one solution that is better for all scenarios, so it might be best to move the time selector out of the top nav and make it the best for the data being displayed.

@jasonish jasonish added this to the 0.20.x milestone Jun 9, 2024
@jasonish jasonish removed this from the 0.20.x milestone Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant