- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.0
- 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
- Accessibility
- Release notes
- Developer guide
Telemetry settings in Kibana
editTelemetry settings in Kibana
editUsage 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 to learn more.
You can control whether this data is sent from the Kibana 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 Kibana via Management > Kibana > Advanced Settings > Usage Data.
General telemetry settings
edit-
telemetry.enabled
-
Set to
true
to send cluster statistics to Elastic. Reporting your cluster statistics helps us improve your user experience. Set tofalse
to disable statistics reporting from any browser connected to the Kibana instance. Defaults totrue
. -
telemetry.sendUsageFrom
-
Set to
'server'
to report the cluster statistics from the Kibana 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 Kibana. Defaults to'server'
. -
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
.
This setting can be changed at any time in Advanced Settings.
-
telemetry.allowChangingOptInStatus
-
Set to
false
to disallow overwriting thetelemetry.optIn
setting via the Advanced Settings in Kibana. Default:true
.
When
false
,telemetry.optIn
must betrue
. To disable telemetry and not allow users to change that parameter, usetelemetry.enabled
.
On this page