Fleet and Elastic Agent 8.1.0
editFleet and Elastic Agent 8.1.0
editReview important information about the Fleet and Elastic Agent 8.1.0 release.
Known issues
editDefault agent policy is no longer created automatically
Details
In prior releases, we provided a default agent policy to make it easier for you to get started quickly. Starting in 8.1.0, the default policy is no longer created automatically; instead, you need to create it explicitly.
Impact
The default policy is no longer available, but we make it easy to create one. To create a default policy, do one of the following:
- In the Add agent flyout, click the Create policy button. If Collect system logs and metrics is selected, Fleet will create a policy that includes the system integration.
- Use the Fleet API or preconfiguration to create the policy. To learn how, refer to Create an agent policy without using the UI.
For self-managed deployments, Fleet Server policy is no longer created automatically
Details
In prior releases, we provided a default Fleet Server policy. Starting in 8.1.0, the default Fleet Server policy is no longer created automatically for self-managed deployments; instead, you need to create it explicitly.
The Elastic Cloud agent policy is not changed; it is still available by default when using our hosted Elasticsearch Service on Elastic Cloud.
Impact
The default Fleet Server policy is no longer available, but we make it easy to create one. To create a Fleet Server policy, do one of the following:
- Use Fleet to Create a policy and add a Fleet Server integration to it.
- Use the Fleet API or preconfiguration to create the policy. To learn how, refer to Create an agent policy without using the UI.
New features
editThe 8.1.0 release adds the following new and notable features.
- Elastic Agent
-
-
Add support for loading input configurations from external configuration files
in standalone mode. You can load inputs from YAML configuration files under the
folder
{path.config}/inputs.d
. #30087
-
Add support for loading input configurations from external configuration files
in standalone mode. You can load inputs from YAML configuration files under the
folder
Enhancements
edit- Fleet