- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.3
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Enterprise Search settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Monitoring settings
- Reporting settings
- Search sessions settings
- Secure settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure logging
- Configure monitoring
- Command line tools
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Data views API
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Cases APIs
- Import and export dashboard APIs
- Logstash configuration management APIs
- Machine learning APIs
- Short URLs APIs
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Troubleshooting
- Accessibility
- Release notes
- Developer guide
Fleet settings in Kibana
editFleet settings in Kibana
editIn Elastic Cloud, Fleet flags are already configured.
You can configure xpack.fleet
settings in your kibana.yml
.
By default, Fleet is enabled. To use Fleet, you also need to configure Kibana and Elasticsearch hosts.
See the Fleet docs for more information.
General Fleet settings
editElastic Package Manager settings
edit-
xpack.fleet.registryUrl
- The address to use to reach the Elastic Package Manager registry.
-
xpack.fleet.registryProxyUrl
- The proxy address to use to reach the Elastic Package Manager registry if an internet connection is not directly available. Refer to Air-gapped environments for details.
Fleet settings
edit-
xpack.fleet.agents.fleet_server.hosts
- Hostnames used by Elastic Agent for accessing Fleet Server.
-
xpack.fleet.agents.elasticsearch.hosts
- Hostnames used by Elastic Agent for accessing Elasticsearch.
-
xpack.fleet.agents.elasticsearch.ca_sha256
- Hash pin used for certificate verification. The pin is a base64-encoded string of the SHA-256 fingerprint.
Preconfiguration settings (for advanced use cases)
editUse these settings to pre-define integrations and agent policies that you want Fleet to load up by default.
-
xpack.fleet.packages
-
List of integrations that are installed when the Fleet app starts up for the first time.
Required properties of
xpack.fleet.packages
-
name
- Name of the integration from the package registry.
-
version
-
Either an exact semantic version, or the keyword
latest
to fetch the latest integration version.
-
-
xpack.fleet.agentPolicies
-
List of agent policies that are configured when the Fleet app starts.
Required properties of
xpack.fleet.agentPolicies
-
id
- Unique ID for this policy. The ID may be a number or string.
-
name
- Policy name.
Optional properties of
xpack.fleet.agentPolicies
-
description
- Text description of this policy.
-
namespace
- String identifying this policy’s namespace.
-
monitoring_enabled
-
List of keywords that specify the monitoring data to collect. Valid values include
['logs']
,['metrics']
, and['logs', 'metrics']
. -
is_managed
-
If
true
, this policy is not editable by the user and can only be changed by updating the Kibana config. -
is_default
-
If
true
, this policy is the default agent policy. -
is_default_fleet_server
-
If
true
, this policy is the default Fleet Server agent policy. -
data_output_id
-
ID of the output to send data. (Need to be identical to
monitoring_output_id
) -
monitoring_output_id
-
ID of the output to send monitoring data. (Need to be identical to
data_output_id
) -
package_policies
-
List of integration policies to add to this policy.
Properties of
package_policies
-
id
- Unique ID of the integration policy. The ID may be a number or string.
-
name
- (required) Name of the integration policy.
-
package
-
(required) Integration that this policy configures.
Properties of
package
-
name
- Name of the integration associated with this policy.
-
-
description
- Text string describing this integration policy.
-
namespace
- String identifying this policy’s namespace.
-
inputs
-
Array that overrides any default input settings for this integration. Follows the same schema as integration inputs, with the exception that any object in
vars
can be passedfrozen: true
in order to prevent that specificvar
from being edited by the user.
-
-
-
xpack.fleet.outputs
-
List of outputs that are configured when the Fleet app starts.
Required properties of
xpack.fleet.outputs
-
id
- Unique ID for this output. The ID should be a string.
-
name
- Output name.
-
type
- Type of Output. Currently we only support "elasticsearch".
-
hosts
- Array that contains the list of host for that output.
-
config
- Extra config for that output.
Optional properties of
xpack.fleet.outputs
-
is_default
-
If
true
, this output is the default output.
Example configuration:
xpack.fleet.packages: - name: apache version: 0.5.0 xpack.fleet.agentPolicies: - name: Preconfigured Policy id: 1 namespace: test package_policies: - package: name: system name: System Integration id: preconfigured-system inputs: - type: system/metrics enabled: true vars: - name: system.hostfs value: home/test streams: - data_stream: dataset: system.core enabled: true vars: - name: period value: 20s - type: winlog enabled: false
-
On this page