Update reporting troubleshooting docs with section about Elastic Maps…

… Service (elastic#99780) * Update reporting troubleshooting docs with section about Elastic Maps Service * Update docs/user/reporting/reporting-troubleshooting.asciidoc Co-authored-by: gchaps <[email protected]> * Update docs/user/reporting/reporting-troubleshooting.asciidoc Co-authored-by: Lisa Cawley <[email protected]> * review feedback Co-authored-by: gchaps <[email protected]> Co-authored-by: Lisa Cawley <[email protected]>
nreese · May 12, 2021 · bb4b186 · bb4b186
1 parent 9b68804
commit bb4b186
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/docs/user/reporting/reporting-troubleshooting.asciidoc b/docs/user/reporting/reporting-troubleshooting.asciidoc
@@ -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}.