# PNG reporting via Curl

**URL:** <https://discuss.elastic.co/t/png-reporting-via-curl/239751>\
**Category:** Kibana\
**Created:** [July 3, 2020, 8:12am UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751 "2020-07-03T08:12:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhelastic](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@mhelastic](https://discuss.elastic.co/u/mhelastic)\
**Post date:** [July 3, 2020, 8:12am UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751/1 "2020-07-03T08:12:12Z")

</div>

Hi There,

We wrote a script that generates and download PDF reports from Kibana visualisations. This script has always been working fantastic. Since we have upgraded to 7.7 and later to 7.8 we get PNG's like this:

 ![Elastic Reporting](https://us1.discourse-cdn.com/elastic/original/3X/1/c/1c7301c032ce93ced358ae252e036544b0b81e61.png)

Some times the PNG's are as expected and sometimes they don't. We have set a timeout of 90 seconds on the rest client that downloads the png's.

We also first check if the PNG is ready before downloading it.

I'm I the only one having this problem or is this a known issue?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [July 3, 2020, 10:13am UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751/2 "2020-07-03T10:13:29Z")

</div>

Kibana internally uses a headless chromium browser to navigate to the right visualization and render it. If the loading screen of Kibana is captured, this means the headless browser didn't have enough time to render the visualization.

A possible reason for this is the machine Kibana is running on doesn't have enough memory - this can slow down the internal browser a lot. You can also try to increase the various timeouts around capturing (e.g. `xpack.reporting.capture.timeouts.openUrl`): [https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-capture-settings](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-capture-settings)

---

<div class="post-metadata">

**Author:** ![mhelastic](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@mhelastic](https://discuss.elastic.co/u/mhelastic)\
**Post date:** [July 3, 2020, 12:45pm UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751/3 "2020-07-03T12:45:43Z")

</div>

Hi Joe,

Thanks for the reply. I tried upgrading the RAM from 1 GB to 2 GB's, but this doesn't solve the problem. We're unable to set the option `xpack.reporting.capture.timeouts.openUrl` because we're using Elastic Cloud. We also tried the options of this topic: [Not allowed to increase reporting capture timeouts in Elastic cloud](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697)

Do you have another suggestion?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [July 3, 2020, 3:35pm UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751/4 "2020-07-03T15:35:59Z")

</div>

2GB is still not much, Chromium is a memory-hungry beast. If 4gb also won't help, please open a support ticket.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 31, 2020, 3:36pm UTC](https://discuss.elastic.co/t/png-reporting-via-curl/239751/5 "2020-07-31T15:36:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.