maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

docs: fix list and a wrong copy/paste (#51908)

Browse source
This commit is contained in:
Marco Vettorello 2019-12-19 17:54:28 +01:00 committed by GitHub
parent 37de142437
commit 5342dd19a4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/user/reporting/reporting-troubleshooting.asciidoc
View file

@ -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`
@ -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`
@ -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.