Skip to content

Commit

Permalink
docs: fix list and a wrong copy/paste (#51908) (#53908)
Browse files Browse the repository at this point in the history
Co-authored-by: Marco Vettorello <[email protected]>
  • Loading branch information
tsullivan and markov00 authored Jan 2, 2020
1 parent 8312e3d commit 44afac2
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions docs/user/reporting/reporting-troubleshooting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ dependencies for Chromium.
Make sure Kibana server OS has the appropriate packages installed for the distribution.

If you are using CentOS/RHEL systems, install the following packages:

* `ipa-gothic-fonts`
* `xorg-x11-fonts-100dpi`
* `xorg-x11-fonts-75dpi`
Expand All @@ -28,6 +29,7 @@ If you are using CentOS/RHEL systems, install the following packages:
* `freetype`

If you are using Ubuntu/Debian systems, install the following packages:

* `fonts-liberation`
* `libfontconfig1`

Expand Down Expand Up @@ -105,9 +107,10 @@ has its own command-line method to generate its own debug logs, which can someti
caused by Kibana or Chromium. See more at https://github.com/GoogleChrome/puppeteer/blob/v1.19.0/README.md#debugging-tips

Using Puppeteer's debug method when launching Kibana would look like:
> Enable verbose logging - internal DevTools protocol traffic will be logged via the debug module under the puppeteer namespace.
> ```
> env DEBUG="puppeteer:*" ./bin/kibana
> ```
```
env DEBUG="puppeteer:*" ./bin/kibana
```
The internal DevTools protocol traffic will be logged via the `debug` module under the `puppeteer` namespace.


The Puppeteer logs are very verbose and could possibly contain sensitive information. Handle the generated output with care.

0 comments on commit 44afac2

Please sign in to comment.