-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Disk Usage visualization always 0 #12435
Comments
This bug seems to come and go between versions. The main problem is Kibana lack of proper "Last Value". Using the "Top Value" aggregation doesn't return the Top Value if there are documents with empty or null values. One way getting around this is by sorting by the same Field and then ordering by timestamp. This same isue happens with CPU and Memory usage in the default Metricbeats Dashboard. I just delete them and use the InfraUI. |
While trying to reproduce this problem, I realized Disk Usage visualization is ordered by |
@kaiyan-sheng I don't think so, probably sorting by value makes more sense. As per the report, pinging @simianhacker here, do you know if the proposed alternative to "Top value" could work better here? |
This may be related to elastic/kibana#16124, where changing the interval to |
@exekias, encountered this recently, it seems that TSVB will in all visualizations except the time series will only show the value of the last data and not the data of the selected time range. So, if no documents are found in the last bucket, value will be 0. Increasing the bucket interval in order to include at least one meaningful doc will fix the issue. Recommendations (thanks @timroes ) are to change the visualization: |
Awesome, Thank you for digging into this! It sounds like increasing the bucket interval would be the smallest change, so visualization keeps its look and feel, WDYT? It seems clear now that this is caused by Do you want to take this? 😇 |
@exekias , I can take this. |
That's true, on the other side, doing the other option would do the average on the whole time range, isn't it? That probably means that for larger ranges (> 15m) the value stops being meaningful, as you probably want the current value, instead of the average for the whole range. It sounds like the What we would really need to fix this once for all would be a way to retrieve the last value for the metric, is that correct? |
That would help imho |
@exekias , I am not sure what the initial goal was but if we are using the time series here and the current setup I assumed we are looking for an average value based on the latest bucket items. A bit about TSVB: In every visualization besides the time series we will only draw the "last bucket" so the value that would be shown very right in the chart of the time series. From the feedback above, it seems that we do not want the whole time range but just the latest value, so the workaround to set to 1min will work only if the users have set interval for filesystem for 1 min. If the goal is to display the latest value here then we will also have to change the aggregation type to "Top Hit" but we still encounter same issues with the interval. |
Thank you for your research! that sounds reasonable to me 👍 I wonder what can we do then for Guage type visualizations (the one on the left of your screenshot) |
Just saw elastic/kibana#3578, which may be helpful with Guage in the future |
Are there any plans to resolve this issue? It has been troubling our users as it provides incorrect monitoring data in the Metricbeat dashboards where these visualizations are used. Currently, possible workarounds are:
|
I'm hitting elastic/kibana#49854 while trying to fix this one, as panel options doesn't seem to get restored when loading the dashboard |
The text was updated successfully, but these errors were encountered: