It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.

The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Add Elasticsearch User Settings Configure Beats and Logstash with Cloud ID »
Elastic Docs ›Elastic Cloud Enterprise Reference [1.1] ›Administering Clusters ›Editing Your User Settings

Add Kibana User Settings

edit

Add Kibana User Settings

edit

Elastic Cloud Enterprise supports most of the standard Kibana and X-Pack settings. Through a YAML editor in the console, you can append Kibana properties to the kibana.yml file. Your changes to the configuration file are read on startup.

Be aware that some settings that could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the latest Kibana settings and syntax.

To change Kibana settings:

  1. Log into the Cloud UI.
  2. Click on a cluster name from the Clusters panel and click Kibana.
  3. In the User Settings section, update the user settings.
  4. Click Save changes.

Saving your changes initiates a configuration plan change that restarts Kibana automatically for you.

If a setting is not supported by Elastic Cloud Enterprise, you will get an error message when you try to save. We suggest changing one setting with each save, so you know which one is not supported.

Example: Set your Kibana landing page

edit

You can specify which Kibana app appears when you open your Kibana endpoint. For example, if you want to open a specific Dashboard every time, simply copy a portion of the URL app/kibana#/{appname}/{appID} and set that as the value.

kibana.defaultAppId: "app/kibana#/dashboard/a8312780-3c3f-11e8-b36a-4f9494701af8"

Example: Increase the timeout for creating reports

edit

When creating reports, you can adjust the number of milliseconds before a worker times out. This is particularly helpful for instances with a slow or heavy load.

xpack.reporting.queue.timeout: "60000"

Example: Change the truncation point for CSV exports

edit

If large exports are causing performance or storage issues, you can increase the number of bytes before the report truncates from the default 10 MB.

xpack.reporting.csv.maxSizeBytes: "20971520"
« Add Elasticsearch User Settings Configure Beats and Logstash with Cloud ID »