New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Fleet and Elastic Agent 8.15.3 Fleet and Elastic Agent 8.15.1 »
Elastic Docs ›Fleet and Elastic Agent Guide [8.15] ›Release notes

Fleet and Elastic Agent 8.15.2

edit

Fleet and Elastic Agent 8.15.2

edit

Review important information about the Fleet and Elastic Agent 8.15.2 release.

Known issues

edit
The memory usage of Beats based integrations is not correctly limited by the number of events actively in the memory queue, but rather the maximum size of the memory queue regardless of usage.

Details

In 8.15, events in the memory queue are not freed when they are acknowledged (as intended), but only when they are overwritten by later events in the queue buffer. This means for example if a configuration has a queue size of 5000, but the input data is low-volume and only 100 events are active at once, then the queue will gradually store more events until reaching 5000 in memory at once, then start replacing those with new events.

See Beats issue #41355.

Impact

Memory usage may be higher than in previous releases depending on the throughput of Elastic Agent. A fix is planned for 8.15.4.

  • The worst memory increase is for low-throughput configs with large queues.
  • For users whose queues were already sized proportionate to their throughput, memory use is increased but only marginally.
  • Affected users can mitigate the higher memory usage by lowering their queue size.

Enhancements

edit
Fleet
  • Bump the maximum supported package spec version to 3.2. (#193574)

Bug fixes

edit
Fleet
  • Prevent extra agent_status call with empty policyId, resulting in incorrect agent count on the Edit Integration page. (#192549)
  • Set the correct title for the Restart upgrade agent modal. (#192536)
Elastic Agent
  • Add the health_check extension to the otel.yml file bundled with the Elastic Agent package, in order to prevent installation of the open-telemetry/opentelemetry-collector Helm chart from failing. #5369 #5092
  • Fix bug that prevented the Beats Elasticsearch output from recovering from an interrupted connection. #40796 #40705
  • Prevent the Elastic Agent from crashing when self unenrolling due to too many authentication failures against Fleet Server. #5438 #5434
  • Set the default log level when an Elastic Agent policy is changed and a log level is not set in the policy. #5452 #5451
Fleet Server
  • Enable missing warnings for configuration options that have been deprecated throughout the 8.x lifecycle. #3901
« Fleet and Elastic Agent 8.15.3 Fleet and Elastic Agent 8.15.1 »

On this page

Was this helpful?
Feedback