-
Notifications
You must be signed in to change notification settings - Fork 24.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
Monitoring>Beats>Overview page causes #49408
Comments
Thanks for opening this issue, but this issue appears to be a user question. We'd like to direct these kinds of things to the forums. If you can stop by there, we'd appreciate it. This allows us to use GitHub for verified bug reports, feature requests, and pull requests. There's an active community in the forums that should be able to assist you with this error. As such, I hope you don't mind that I close this. |
@martijnvg I understand that such cases should be put up on forums first. However, the error seemed very similar to the one addressed in elastic/kibana#49978 That is why I thought I should directly open an issue here than go to forums. |
This kind of error indicates that a certain search request with aggregations generates too many buckets. There are several to the get around this. This is why I redirected you to the forums. |
@martijnvg I am well aware of what the error indicate. I also understand users can cause this error by configuring the system incorrectly. However, as this is happening on a monitoring page which is part of X-Pack, I believe this can possibly be a misconfiguration on the part of Elastic team. That is why I thought it might just be better to open an issue. |
@amitavmohanty01 I see, I think then it is better to open an issue in the Kibana repository. Perhaps the search request that is executed as part of that page needs to be tuned. |
Elasticsearch version (
bin/elasticsearch --version
):7.4.2Plugins installed: [mapper-size]
JVM version (
java -version
):8OS version (
uname -a
if on a Unix-like system):Cent OS 7Description of the problem including expected versus actual behavior:
The Monitoring>Beats>Overview page fails to load.
Steps to reproduce:
Load the path
/app/monitoring#/beats
Provide logs (if relevant):
It causes the following exceptions in the logs.
The text was updated successfully, but these errors were encountered: