kibana/docs/settings/fleet-settings.asciidoc
2020-12-17 12:23:16 -08:00

51 lines
1.2 KiB
Text

[role="xpack"]
[[fleet-settings-kb]]
=== {fleet} settings in {kib}
++++
<titleabbrev>{fleet} settings</titleabbrev>
++++
experimental[]
You can configure `xpack.fleet` settings in your `kibana.yml`.
By default, {fleet} is enabled. To use {fleet}, you also need to configure {kib} and {es} hosts.
See the {fleet-guide}/index.html[{fleet}] docs for more information.
[[general-fleet-settings-kb]]
==== General {fleet} settings
[cols="2*<"]
|===
| `xpack.fleet.enabled` {ess-icon}
| Set to `true` (default) to enable {fleet}.
| `xpack.fleet.agents.enabled` {ess-icon}
| Set to `true` (default) to enable {fleet}.
|===
[[fleet-data-visualizer-settings]]
==== {package-manager} settings
[cols="2*<"]
|===
| `xpack.fleet.registryUrl`
| The address to use to reach {package-manager} registry.
|===
==== {fleet} settings
[cols="2*<"]
|===
| `xpack.fleet.agents.kibana.host`
| The hostname used by {agent} for accessing {kib}.
| `xpack.fleet.agents.elasticsearch.host`
| The hostname used by {agent} for accessing {es}.
| `xpack.fleet.agents.tlsCheckDisabled`
| Set to `true` to allow {fleet} to run on a {kib} instance without TLS enabled.
|===
[NOTE]
====
In {ecloud}, {fleet} flags are already configured.
====