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
Automatically generate ranges for range/histogram agg #3757
Comments
I mentioned the range agg, but now I think these enhancements might as well (possibly better) fit the histogram agg. |
+1 With the field stats api, we could quickly get the min and max values for a field as the first query to help build out the ranges automatically before sending the query in. |
For reference, here is the ES enhancement ticket: elastic/elasticsearch#9572 |
Just adding that occasionally, the binning is not determined based on fixed interval of the independent variable, but on quantiles. An often used quantile is the quartile, eg. showing IQR (interquartile ranges. Boxplots usually derive from IQR values and by extension, their continuous adaptation, bandlines too. Ticket #3905 is also related. There are also histogram types where it's not the "height" but the "width" that varies, ie. widths are determined in line with probabilities, a way of showing quantile data. Sticking to the plain variety of histograms, some method is often used to automatically determine the histogram bin count based on a calculation, eg. the Sturges' formula. |
+1 on @monfera's point being able to generate the X-axis bucketing automatically by percentiles of a value. The percentile distribution type of histogram is how most changes and AB tests are evaluated for me these days. For these use cases we have to make use of Tableau today. |
We don't automatically generate ranges for the |
In some cases it would be very useful to have Kibana generate the ranges used for the range agg with simple rules, for example:
The second example is especially useful to plot a distribution of latencies with a long tail.
The text was updated successfully, but these errors were encountered: