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

Update reporting troubleshooting docs with section about Elastic Maps Service (#99780)

Browse source 
* Update reporting troubleshooting docs with section about Elastic Maps Service

* Update docs/user/reporting/reporting-troubleshooting.asciidoc

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>

* Update docs/user/reporting/reporting-troubleshooting.asciidoc

Co-authored-by: Lisa Cawley <lcawley@elastic.co>

* review feedback

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
This commit is contained in:
Nathan Reese 2021-05-12 15:20:47 -06:00 committed by GitHub
parent 9b68804e0c
commit bb4b186811
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -16,6 +16,7 @@ Having trouble? Here are solutions to common problems you might encounter while
* <<reporting-troubleshooting-puppeteer-debug-logs>>
* <<reporting-troubleshooting-system-requirements>>
* <<reporting-troubleshooting-arm-systems>>
* <<reporting-troubleshooting-maps-ems>>
[float]
[[reporting-diagnostics]]
@ -163,3 +164,12 @@ In this case, try increasing the memory for the {kib} instance to 2GB.
=== ARM systems
Chromium is not compatible with ARM RHEL/CentOS.
[float]
[[reporting-troubleshooting-maps-ems]]
=== Unable to connect to Elastic Maps Service
https://www.elastic.co/elastic-maps-service[{ems} ({ems-init})] is a service that hosts
tile layers and vector shapes of administrative boundaries.
If a report contains a map with a missing basemap layer or administrative boundary, the {kib} server does not have access to {ems-init}.
See <<maps-connect-to-ems>> for information on how to connect your {kib} server to {ems-init}.