a729b3baef
* Remove support for deprecated xpack.telemetry configurations In 7.5, we moved telemetry to OSS and dropped the xpack prefix for the telemetry plugin configuration options. We deprecated the usage of the xpack prefix so any existing usage would trigger a warning at startup. In 8.0, we remove support for the deprecated xpack prefix configs for telemetry. * Move telemetry settings into its own document * Use external reference instead of anchor * Update docs/migration/migrate_8_0.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/migration/migrate_8_0.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/settings/telemetry-settings.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Remove depecrated xpack.telemetry.* config from xpack_main/index.js Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com> Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
39 lines
1.9 KiB
Plaintext
39 lines
1.9 KiB
Plaintext
[[telemetry-settings-kbn]]
|
|
=== Telemetry settings in Kibana
|
|
++++
|
|
<titleabbrev>Telemetry settings</titleabbrev>
|
|
++++
|
|
|
|
By default, Usage Collection (also known as Telemetry) is enabled. This
|
|
helps us learn about the {kib} features that our users are most interested in, so we
|
|
can focus our efforts on making them even better.
|
|
|
|
You can control whether this data is sent from the {kib} servers, or if it should be sent
|
|
from the user's browser, in case a firewall is blocking the connections from the server. Additionally, you can decide to completely disable this feature either in the config file or in {kib} via *Management > Kibana > Advanced Settings > Usage Data*.
|
|
|
|
See our https://www.elastic.co/legal/privacy-statement[Privacy Statement] to learn more.
|
|
|
|
[float]
|
|
[[telemetry-general-settings]]
|
|
==== General telemetry settings
|
|
|
|
`telemetry.enabled`:: *Default: true*.
|
|
Set to `true` to send cluster statistics to Elastic. Reporting your
|
|
cluster statistics helps us improve your user experience. Your data is never
|
|
shared with anyone. Set to `false` to disable statistics reporting from any
|
|
browser connected to the {kib} instance.
|
|
|
|
`telemetry.sendUsageFrom`:: *Default: 'browser'*.
|
|
Set to `'server'` to report the cluster statistics from the {kib} server.
|
|
If the server fails to connect to our endpoint at https://telemetry.elastic.co/, it assumes
|
|
it is behind a firewall and falls back to `'browser'` to send it from users' browsers
|
|
when they are navigating through {kib}.
|
|
|
|
`telemetry.optIn`:: *Default: true*.
|
|
Set to `true` to automatically opt into reporting cluster statistics. You can also opt out through
|
|
*Advanced Settings* in {kib}.
|
|
|
|
`telemetry.allowChangingOptInStatus`:: *Default: true*.
|
|
Set to `true` to allow overwriting the `telemetry.optIn` setting via the {kib} UI.
|
|
Note: When `false`, `telemetry.optIn` must be `true`. To disable telemetry and not allow users to change that parameter, use `telemetry.enabled`.
|