WARNING: Version 6.2 of Kibana has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Configuring Reporting
editConfiguring Reporting
editIf you use a reverse-proxy (NGINX, Apache, etc.) to access Kibana, you need to configure the Kibana server settings
By default, a new encryption key is generated for X-Pack reporting each time you start Kibana. This means any pending reports will fail if you restart Kibana.
To set a static encryption key for reporting, set the
xpack.reporting.encryptionKey property in the kibana.yml
configuration file. You can use any text string as the encryption key.
xpack.reporting.encryptionKey: "something_secret"
If you are load balancing across multiple Kibana instances, they need to have the same reporting encryption key. Otherwise, report generation will fail if a report is requested through one instance and another instance picks up the job from the report queue.
You can also configure settings in kibana.yml to control how X-Pack reporting
communicates with the Kibana server, manages background jobs, and captures
screenshots. See Reporting Settings for the complete
list of settings.