-
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
[Metrics UI] Make composite size configurable to avoid max buckets #72955
[Metrics UI] Make composite size configurable to avoid max buckets #72955
Conversation
@hendry-lim @cauemarcondes Can you check to see if this fixes the issue you're having? I wasn't able to reproduce it locally but based on the error you're seeing in #72367 I'm confident it will fix it. |
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
@simianhacker I just tried to set up my Kibana dev environment, but failed at |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…lastic#72955) Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…lastic#72955) Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
This PR fixes #72367 by decreasing the composite aggregation size to 5 to avoid the "max bucket issue" for the Metrics UI request for the Observability homepage. The buckets are calculated by
{number of buckets} * ({number of network traffic metrics} * 10) * {composite aggregation size}
In the "real world" that works out to be180 * 20 * 75
which is beyond themax_bucket
default threshold of 20000.Checklist
Delete any items that are not applicable to this PR.