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.
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:
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.