Kibana 8.8.2
editKibana 8.8.2
editReview the following information about the Kibana 8.8.2 release.
Known issues
editKibana can run out of memory during an upgrade when there are many Fleet agent policies.
Details
Due to a schema version update, during Fleet setup in 8.8.x, all agent policies are being queried and deployed.
This action triggers a lot of queries to the Elastic Package Registry (EPR) to fetch integration packages. As a result,
there is an increase in Kibana’s resident memory usage (RSS).
Impact
Because the default batch size of 100
for schema version upgrade of Fleet agent policies is too high, this can
cause Kibana to run out of memory during an upgrade. For example, we have observed 1GB Kibana instances run
out of memory during an upgrade when there were 20 agent policies with 5 integrations in each.
Workaround
Two workaround options are available:
- Increase the Kibana instance size to 2GB. So far, we are not able to reproduce the issue with 2GB instances.
-
Set
xpack.fleet.setup.agentPolicySchemaUpgradeBatchSize
to2
in thekibana.yml
and restart the Kibana instance(s).
In 8.9.0, we are addressing this by changing the default batch size to 2
.
Bug Fixes
edit- APM
-
- Fixes the latency graph displaying all service transactions, rather than the selected one, on the transaction detail page #159085
- Dashboard
- Elastic Security
- For the Elastic Security 8.8.2 release information, refer to Elastic Security Solution Release Notes.
- Enterprise Search
- For the Elastic Enterprise Search 8.8.2 release information, refer to Elastic Enterprise Search Documentation Release notes.
- Fleet
- Logs
-
- Fixes log categorization UI failure due to an infinite loop #159090
- Machine Learning
- Maps
- Monitoring
-
- Permanently hide the telemetry notice on dismissal #159893
- Observability
-
- Handle buildEsQuery error (such as leading wildcard) in status change #159891
- Platform
- Uptime