New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« PDF Layout Modes Reporting and Security »
Elastic Docs ›Kibana User Guide [6.3] ›Reporting from Kibana

Configuring Reporting

edit

Configuring Reporting

edit

If 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.

« PDF Layout Modes Reporting and Security »
Was this helpful?
Feedback