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.11.2 Fleet and Elastic Agent 8.11.0 »
Elastic Docs ›Fleet and Elastic Agent Guide [8.11] ›Release notes

Fleet and Elastic Agent 8.11.1

edit

Fleet and Elastic Agent 8.11.1

edit

Review important information about Fleet Server and Elastic Agent for the 8.11.1 release.

Due to a memory leak issue, Windows users running Elastic Agent are recommended to avoid upgrading to this release and waiting for the upcoming 8.11.2 release in which the issue is resolved. If you’ve already upgraded to version 8.11.0 or 8.11.1, we recommend upgrading to 8.11.2 as soon as it becomes available. See the known issue for more detail.

Known issues

edit
  • The known issue that could prevent the Elastic Agent or Integrations Server component from booting up within an ECE deployment has been resolved in this release.
Memory leak running Elastic Agent in Windows environments with the System Integration

Details

A memory leak has been identified in Beats on Windows. All Beats running Elastic Stack version 8.11.0 or 8.11.1 are affected. The leak also affects the Elastic Agent System integration which is implemented with Beats. The leak will eventually exhaust all memory on the host system, typically after several days.

Impact

This issue has been fixed in version 8.11.2. For a Windows environment, we strongly recommend upgrading directly to 8.11.2 or any later release.

If you’re already running Elastic Agent version 8.11.0 or 8.11.1 on Windows and do not want to upgrade, we recommend that you:

  1. Disable the process and process_summary metrics in your System integration.
  2. Disable logs and metrics collection.
  3. Restart Elastic Agent.

Note that disabling these datasets will prevent the collection of process-related metrics.

Another workaround is to downgrade Elastic Agent to a version below 8.11.0. Note that this could result in missing or reindexed logs or metrics as the "state" will not be persisted after Elastic Agent is uninstalled and reinstalled.

For Beats we currently do not have a workaround apart from upgrading to 8.12.2 or a later release.

Current stack version is not in the list of Elastic Agent versions in Kibana Fleet UI

Details

On the Fleet UI in Kibana:

  • When adding a new Elastic Agent, the user interface shows a previous version instead of the current version.
  • When attempting to upgrade, the modal window to pick the version shows an earlier version as the latest version.

Impact

You can use the following steps as a workaround:

When upgrading Elastic Agent currently on versions 8.10.4 or lower (simpler)

  1. Open the Fleet UI. Under the Agents tab select Upgrade agent from the actions menu. The version field in the Upgrade agent UI allows you to enter any version.
  2. Enter 8.11.0 or whichever version you want to upgrade the [agents] to. Do not choose a version above the version of Kibana or Fleet Server that you’re running.

When upgrading Elastic Agent currently on any version (more complex, requires API)

  1. Open Kibana and navigate to Management → Dev Tools.

  2. Choose one of the API requests below and submit it through the console. Each of the requests uses version 8.11.0 as an example, but this can be changed to any available version.

    • To upgrade a single Elastic Agent to any version, run:

      POST kbn:/api/fleet/agents/<Elastic Agent ID>/upgrade
{"version":"8.11.0"}
      Copy as curlTry in Elastic 

    • To upgrade a set of Elastic Agents based on a known set of agent IDs, run:

      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "version":"8.11.0",
  "agents":["<Elastic Agent ID>","<Another Elastic Agent ID>"],
  "start_time":"2023-11-10T09:41:39.850Z"
}
      Copy as curlTry in Elastic 

    • To upgrade a set of Elastic Agents running a specific policy, and below a specific version (for example, 8.11.0), run:

      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "agents": "fleet-agents.policy_id:<Elastic Fleet Policy ID> and fleet-agents.agent.version<<VERSION>",
  "version": "8.11.0"
}
      Copy as curlTry in Elastic 
      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "agents": "fleet-agents.policy_id:uuid1-uuid2-uuid3-uuid4 and fleet-agents.agent.version<8.11.0",
  "version": "8.11.0"
}
      Copy as curlTry in Elastic 

To find the ID for any Elastic Agent, open the Agents tab in Fleet and select View agent from the Actions menu. The agent ID and other details are shown.

To learn more about these requests, refer to the Fleet API documentation.

New features

edit

The 8.11.1 release Added the following new and notable features.

Elastic Agent
  • Add the dimensions component.id and component.binary to Elastic Agent and Beats monitoring output, to support unique entries for the Time Series Database (TSDB) feature. #3626 #7977

Bug fixes

edit
Fleet
  • Append space ID to security solution tag. (#170789).
  • Modify bulk unenroll to include inactive agents. (#170249).
« Fleet and Elastic Agent 8.11.2 Fleet and Elastic Agent 8.11.0 »

On this page

Was this helpful?
Feedback