kibana/docs/reference/configuration-reference/telemetry-settings.md
Colleen McGinnis 1814c60017
[docs] Migrate docs from AsciiDoc to Markdown (#212558)
Migrate docs from AsciiDoc to Markdown. The preview can be built after
#212557 is merged.

@florent-leborgne please tag reviewers, add the appropriate label(s),
and take this out of draft when you're ready.

Note: More files are deleted than added here because the content from
some files was moved to
[elastic/docs-content](https://github.com/elastic/docs-content).

**What has moved to
[elastic/docs-content](https://github.com/elastic/docs-content)?**

Public-facing narrative and conceptual docs have moved. Most can now be
found under the following directories in the new docs:
- explore-analyze: Discover, Dashboards, Visualizations, Reporting,
Alerting, dev tools...
- deploy-manage: Stack management (Spaces, user management, remote
clusters...)
- troubleshooting: .... troubleshooting pages

**What is staying in the Kibana repo?**

- Reference content (= anything that is or could be auto-generated):
Settings, syntax references
- Release notes
- Developer guide

---------

Co-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>
2025-03-04 14:56:07 +01:00

33 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
navigation_title: "Telemetry settings"
mapped_pages:
- https://www.elastic.co/guide/en/kibana/current/telemetry-settings-kbn.html
---
# Telemetry settings in {{kib}} [telemetry-settings-kbn]
Usage Collection (also known as Telemetry) is enabled by default. This allows us to learn what our users are most interested in, so we can improve our products and services.
Refer to our [Privacy Statement](https://www.elastic.co/legal/product-privacy-statement) to learn more.
You can control whether this data is sent from the {{kib}} servers, or if it should be sent from the users browser, in case a firewall is blocking the connections from the server. Additionally, you can disable this feature either in **Stack Management > {{kib}} > Advanced Settings > Global Settings > Usage collection** or the config file with the following settings.
## General telemetry settings [telemetry-general-settings]
$$$telemetry-optIn$$$ `telemetry.optIn`
: Set to `false` to stop sending any telemetry data to Elastic. Reporting your cluster statistics helps us improve your user experience. **Default: `true`.**<br>
This setting can be changed at any time in [Advanced Settings](/reference/advanced-settings.md). To prevent users from changing it, set [`telemetry.allowChangingOptInStatus`](/reference/configuration-reference/general-settings.md#telemetry-allowChangingOptInStatus) to `false`.
`telemetry.allowChangingOptInStatus`
: Set to `false` to disallow overwriting the [`telemetry.optIn`](#telemetry-optIn) setting via the [Advanced Settings](/reference/advanced-settings.md) in {{kib}}. **Default: `true`.**
`telemetry.sendUsageFrom`
: 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/](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}}. **Default: `'server'`.**
`xpack.apm.telemetryCollectionEnabled`
: Collects information about APM data and API performance. Set this to `false` to specifically disable APMs collector. **Default: `'true'`.**