# X-pack :-Report : PDF generated report in the mail attached is getting corrupted

**URL:** https://discuss.elastic.co/t/x-pack-report-pdf-generated-report-in-the-mail-attached-is-getting-corrupted/91080
**Category:** Elasticsearch
**Created:** [June 28, 2017, 10:28am UTC](https://discuss.elastic.co/t/x-pack-report-pdf-generated-report-in-the-mail-attached-is-getting-corrupted/91080 "2017-06-28T10:28:35Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)
#### Post date: [July 18, 2017, 5:16pm UTC](https://discuss.elastic.co/t/x-pack-report-pdf-generated-report-in-the-mail-attached-is-getting-corrupted/91080/6 "2017-07-18T17:16:40Z")

</div>

In 5.4.x, there's a couple ways to get logs.

You can see _all_ of the debugging logs by adding `logging.verbose: true` to your kibana.yml file. This will show you a ton of information, certainly more than you care about, which will probably make it hard to pick out the information you care about.

You can also specify exactly what kind of logs you want to see in the output. It seems to be undocumented, but it's pretty simple. In this case, you want to see `reporting` and `phantomConsole` logs. You can add the following to your kibana.yml file, which should give you this output:

```auto
logging.events.logs: ['reporting', 'phantomConsole']

```

Note that this will stop all of the normal output, including info, warnings, and errors. If you'd like to continue to see that as well, use this:

```auto
logging.events.logs: ['info', 'warning', 'error', 'fatal', 'reporting', 'phantomConsole']

```

Once you've got that set up, restart Kibana to load the new config and manually generate a report, using the UI in visualize or dashboard. Whatever you manually did before is fine. Now if you check the output from the Kibana server, you'll see some reporting and phantom output, including the URLs being requested, any failures in the response, or failures loading the page, etc. This should help determine what is causing the report to error out. If you can't make sense of it, post the output here and I should be able to offer up a solution.

---

_[View the full topic](https://discuss.elastic.co/t/x-pack-report-pdf-generated-report-in-the-mail-attached-is-getting-corrupted/91080)._