-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Support for auto-refresh #1845
Comments
+1, this would be very useful. |
👍 |
+1 for this, we use a Kibana dashboard as a non-interactive "bird-eye view" of our processes and we cannot migrate to v. 4 until auto-refresh feature is not implemented. |
👍 |
2 similar comments
👍 |
👍 |
👍 |
👍 |
This would be extremely useful for us as well. I was going down the path of some hackish-customizations in order to get visualizations from separate indices & queries on the same dashboard; now that it's supported in Kibana 4, having the ability to create a dashboard and refresh the charts at a given interval allows us to use it on the static status monitors. |
+1 |
2 similar comments
👍 |
👍 |
+1, it is a showstopper for K4 adoption over K3 for several of my clients. |
+1 |
+1, absolutely. Auto-refresh is one of the most important features of Kibana 3, and needs to be in Kibana 4 ASAP. |
+1 |
This is a deal-breaker for us. |
+1 |
6 similar comments
+1 |
+1 |
👍 |
+1 |
+1 |
+1 |
+1 |
1 similar comment
+1 |
+1 |
+1 Happy to have this enhancement in Kibana 4 |
👍 |
@rashidkpc Can you share any details about the feasibility/costs of implementing this in Kibana 4? Definitely looking forward to this feature being added :-). Thanks. |
+1 |
6 similar comments
👍 |
+1 |
+1 |
+1 |
👍 |
+1 |
Timefilter Auto Refresh - Closes "Support for auto-refresh #1845"
+1 please |
+1 |
+1, please get this in asap. |
+1 |
2 similar comments
👍 |
+1 |
While Kibana 4 might have many more features than 3, it lacks basic functionalities such as auto-refresh for a dashboard tool. Plus, the dashboard's look and feel is a few levels below 3. |
This was already fixed, probably worth locking this issue /cc @rashidkpc |
+1 |
Everybody said +1 for this feature, I agree it is worth having this feature but I would like to have a config toggle for this. because it causes a drain of tomcat/ES resources when you have 50 clients connecting to the node on which ES and tomcat running. |
+1 |
+1 for @skshandilya comment |
+1 |
This was a nice feature in Kibana 3. Realize you have a lot of feature requests and have to prioritize, but for what its worth this would be useful in 4 as well.
The text was updated successfully, but these errors were encountered: