# Kibana Instance Crashing During PDF/CSV Export on Elastic Cloud **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security, elastic-stack-reporting, elastic-stack-alerting, user-experience\ **Created:** [February 10, 2026, 9:48am UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990 "2026-02-10T09:48:33Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Hichem\_Blagui](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hichem\_Blagui](https://discuss.elastic.co/u/Hichem_Blagui)\ **Post date:** [February 10, 2026, 9:48am UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990/1 "2026-02-10T09:48:33Z")
Hi, I am experiencing frequent instance crashes when attempting to export default dashboards (PDF/PNG/CSV) from Kibana. I am currently using Elastic Cloud and do not have access to the underlying terminal or the physical kibana.yml file to adjust server settings. Example of Report causing the crash: ![report generation](https://us1.discourse-cdn.com/elastic/original/3X/3/5/3522fc3bc8813c289669ec1b590052978913d6e2.png) This results in the instance crashing with 502 bad gateway error message from Nginx. I would like to implement best practices to stabilize these exports. Specifically, I am looking for the correct way to apply the following via the Elastic Cloud Console's "User settings overrides": Reporting Timeouts: Increasing xpack.reporting.queue.timeout to allow more time for complex dashboard rendering. Memory Allocation: Since I cannot set NODE\_OPTIONS via terminal, what is the recommended way to ensure Kibana has enough RAM for heavy X-Pack reporting tasks on Cloud? CSV Size Limits: Safely adjusting xpack.reporting.csv.maxSizeBytes without destabilizing the node. PDF Size Limits: **`xpack.reporting.queue.timeout, xpack.reporting.kibanaServer.hostname and xpack.reporting.thumbnails.enabled: false`** Could you provide an example of the YAML snippet I should paste into the Kibana user settings section of my deployment to fix this? Environment: Deployment: Elastic Cloud (Hosted) Version: kibana 9.3.0 ---
**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\ **Post date:** [February 11, 2026, 8:13am UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990/2 "2026-02-11T08:13:55Z")
Hello @Hichem_Blagui Welcome to the Community!! Below documentation could help to understand all the available settings : > **[Reporting and sharing | Elastic Docs](https://www.elastic.co/docs/explore-analyze/report-and-share)** > > Kibana provides you with several options to share Discover sessions, Dashboards, Visualize Library visualizations, and Canvas workpads. These sharing... > **[Reporting settings in Kibana | Kibana](https://www.elastic.co/docs/reference/kibana/configuration-reference/reporting-settings)** > > You can configure xpack.reporting settings to: Enable or disable the reporting features, Configure an encryption key to protect sensitive authentication... In the Kibana logs what is the reason for it to crash , this could help us understand if the memory available is not sufficient or it needs to be increased at node level? If the memory is not sufficient i believe updating below parameters might still not help & the instance might crash. The memory available for Kibana can be checked via ECE console & monitor the Memory Size via Stack Monitoring : From the documentation we see that default is 4m / 250mb you will have to modify as per your environment/performance : ```auto xpack.reporting.queue.timeout : 8m (if you want to increase this to 8m) xpack.reporting.csv.maxSizeBytes: 524288000 (if you want to increase this to 500mb) xpack.reporting.kibanaServer.hostname => Optional as per documentation ``` Thanks!! ---
**Author:** ![Hichem\_Blagui](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hichem\_Blagui](https://discuss.elastic.co/u/Hichem_Blagui)\ **Post date:** [February 12, 2026, 8:24am UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990/3 "2026-02-12T08:24:38Z")
> [@Tortoise](#): > > In the Kibana logs what is the reason for it to crash , this could help us understand if the memory available is not sufficient or it needs to be increased at node level? > If the memory is not sufficient i believe updating below parameters might still not help & the instance might crash. I no longer have access to the instance, but my prior investigation showed no internal logs regarding the incident. This suggests the root cause is likely either a JVM Heap issue related to memory allocation or a misconfiguration within the Nginx proxy of the instance itself. PS: Stack Monitoring shows no changes before the crash. ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [February 12, 2026, 1:59pm UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990/4 "2026-02-12T13:59:57Z")
> [@Hichem\_Blagui](#): > > This suggests the root cause is likely either a JVM Heap issue related to memory allocation or a misconfiguration within the Nginx proxy of the instance itself Have you opened a support case with Elastic ? ---
**Author:** ![Hichem\_Blagui](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@Hichem\_Blagui](https://discuss.elastic.co/u/Hichem_Blagui)\ **Post date:** [February 12, 2026, 2:07pm UTC](https://discuss.elastic.co/t/kibana-instance-crashing-during-pdf-csv-export-on-elastic-cloud/384990/5 "2026-02-12T14:07:28Z")
Noted. I hadn't pursued a case given the terminated status of the deployment. I'll re-evaluate based on the snapshot availability.