This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
The settings described here are configurable through the Fleet UI. Refer to
Fleet settings in Kibana for a list of
settings that you can configure in the
kibana.yml configuration file.
Configure Fleet settings to apply global settings to all Elastic Agents enrolled in Fleet:
- In Kibana, open the main menu, then click Management > Fleet.
Click Fleet settings
The URLs your Elastic Agents will use to connect to a Fleet Server. This setting is required. On self-managed clusters, you must specify one or more URLs. On Elastic Cloud, this field is populated automatically.
If a URL is specified without a port, Kibana sets the port to
By default, Fleet Server is typically exposed on the following ports:
- Default Fleet Server port for self-managed clusters
- Default Fleet Server port for Elastic Cloud. Look at Fleet settings to see the actual port that’s used.
The exposed ports must be open for ingress and egress in the firewall and networking rules on the host to allow Elastic Agents to communicate with Fleet Server.
Specify multiple URLs to scale out your deployment and provide automatic failover.
If multiple URLs exist, Fleet shows the first provided URL for enrollment purposes. Enrolled Elastic Agents will connect to the URLs in round robin order until they connect successfully.
When a Fleet Server is added or removed from the list, all agent policies are updated automatically.
The Elasticsearch URLs where Elastic Agents will send data. By default, Elasticsearch is exposed on the following ports:
- Default Elasticsearch port for self-managed clusters
- Default Elasticsearch port for Elastic Cloud
YAML settings that will be added to the Elasticsearch output section of each policy. This setting allows you to specify global output settings for all Elastic Agents enrolled in Fleet. Make sure you specify valid YAML. The UI does not currently provide validation.
- Save and apply the settings.