Context:

Due to the limitations of our bucket limit implementation some edge cases can lead to ES attempting to create too many buckets (this happens for example due to rounding when creating number variable range aggregations).
Currently, when this happens, the UI would just display the exception which might confuse users who may not be aware that they can solve the issue by applying filters or readjusting the custom bucket size.
Let's see if we can define an error code and add a better exception message before handing off to the frontend.

AT:

• too_many_bucket_exceptions are being handled in a way that makes it more transparent for the user in the UI how to solve the issue by reconfiguring the report