You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During a serverless scale test, some elastic agent containers consumed more memory than expected, and a lot of this additional consumption was caused by the metricbeat elasticsearch module. The Nodes in question had in the order of ~50 Elasticsearch Pods on them, which is definitely an edge case, but @miltonhultgren indicated this could likely be significantly improved. I'm opening this issue to track those potential improvements separately from changes to agent itself. See elastic/elastic-agent#5991 for more context.
If nothing else, it would be good to have a synthetic benchmark for this module.
The text was updated successfully, but these errors were encountered:
Describe the enhancement:
During a serverless scale test, some elastic agent containers consumed more memory than expected, and a lot of this additional consumption was caused by the metricbeat elasticsearch module. The Nodes in question had in the order of ~50 Elasticsearch Pods on them, which is definitely an edge case, but @miltonhultgren indicated this could likely be significantly improved. I'm opening this issue to track those potential improvements separately from changes to agent itself. See elastic/elastic-agent#5991 for more context.
If nothing else, it would be good to have a synthetic benchmark for this module.
The text was updated successfully, but these errors were encountered: