-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Time-based navigation #1956
Comments
Agreed, would be a nice feature. |
👍 |
2 similar comments
👍 |
👍 |
👍 |
A zoom out button would be really useful. Also, a time picket in embeded dashboards |
👍 |
+1 the "zoom out" feature from kibana 3 is missing |
+1 for the zoom out function. This would save us a lot of time manually updating the date/time range. I guess one implementation would be to take the absolute timespan currently selected and remove from the "from" and add to the "to" range values. |
Hidden in 5.2, plan to expose in 5.3. |
I'm using Kibana 3 and 4 for historical log analysis. A common flow for me is to set the time window to a business day, then zoom in until I get to maybe a time window (anywhere between 2 hours and 5 minutes) where the graphs show me what I need to know. Often I then want to navigate forward and backward through time, watching how stats change.
In Kibana 3 I have to either remove time filters and add new ones or edit the main time field.
In Kibana 4 I'm editing the main time picker.
What I'd love is the following: a + and - button by the time picker which function as follows. + takes the difference between the current start and end range and adds that difference to both fields. I could also imagine a 1/2+ (better name needed) which advances half the current time window, to allow a bit of context to remain. Perhaps also of use would be a +Day to keep the current time, but advance one day.
Happy enough if my workflow isn't very common or there's a better way of doing this. I think I can implement what I need in Kibana 4 through bookmarklets if necessary.
The text was updated successfully, but these errors were encountered: