Fleet and Elastic Agent 7.16.0edit
Review important information about the Fleet and Elastic Agent 7.16.0 releases.
Enhancementsedit
- Fleet
-
- Adds prompt for users to add an agent if they add an integration to an agent policy with no agents #114830
- Allow users with read access to view Integrations app #113925
- Removes enterprise license requirement for custom registry URL #113858
- Adds "Keep Policies up to Date" functionality for integrations #112702
- Allow packages to specify index privileges #112397
- Allow Integrations browse page to filter on descriptions #111649
- Support automatic upgrades of package policies when updating integrations #108269
- Allow preconfiguration of alternative Elasticsearch outputs #111002
- Elastic Agent
Bug fixesedit
- Fleet
-
- Link to the installed version of an integration from global search #115736
- Fixes agent count in update modal #114622
- Shows security requirements page when Elasticsearch security is not enabled #114583
- Improves default settings for Fleet component templates #114101
-
Report
installingstatus while package install is in progress #111875
Known issuesedit
Naming conflict during agent policy creation may result in policy with no system integration
Details
There is a bug in the logic used to create unique integration policy names. If you edit a system integration in an existing agent policy, and then try to create a new agent policy with Collect logs and metrics selected, you’ll see the error message, "There is already a package with the same name". #121059
Impact
The new agent policy will be created, but it will not include the system integration, and it will be unable to collect logs and metrics.
Workaround
You can either:
- Manually add the system integration after creating the agent policy
- Rename the other system integration policies and use unique names
Integration policy names must be globally unique
Details
Starting in 7.16.0, integration policy names must be globally unique.
Impact
If you are upgrading from a previous version and have integrations with duplicate names, you’ll encounter an error when you attempt to upgrade the integration: "There is already a package with the same name."
Workaround
You must modify all integration policy names to be unique before trying to upgrade integrations.