[maps][docs] add trouble shooting for index not listed (#73066)

* [maps][docs] add troubeshooting for index not listed * Update docs/maps/trouble-shooting.asciidoc Co-authored-by: gchaps <[email protected]> * Update docs/maps/trouble-shooting.asciidoc Co-authored-by: gchaps <[email protected]> * Update docs/maps/trouble-shooting.asciidoc Co-authored-by: gchaps <[email protected]> * Update docs/maps/trouble-shooting.asciidoc Co-authored-by: gchaps <[email protected]> * Update docs/maps/trouble-shooting.asciidoc Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]>
elastic · Jul 23, 2020 · 849bbfd · 849bbfd
1 parent e359c9a
commit 849bbfd
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/docs/maps/trouble-shooting.asciidoc b/docs/maps/trouble-shooting.asciidoc
@@ -20,6 +20,20 @@ image::maps/images/inspector.png[]
 [float]
 === Solutions to common problems
 
+[float]
+==== Index not listed when adding layer
+
+* Verify your geospatial data is correctly mapped as {ref}/geo-point.html[geo_point] or {ref}/geo-shape.html[geo_shape].
+  ** Run `GET myIndexPatternTitle/_field_caps?fields=myGeoFieldName` in <<console-kibana, Console>>, replacing `myIndexPatternTitle` and `myGeoFieldName` with your index pattern title and geospatial field name.
+  ** Ensure response specifies `type` as `geo_point` or `geo_shape`.
+* Verify your geospatial data is correctly mapped in your <<managing-fields, Kibana index pattern>>.
+  ** Open your index pattern in <<management, Stack Management>>.
+  ** Ensure your geospatial field type is `geo_point` or `geo_shape`.
+  ** Ensure your geospatial field is searchable and aggregatable.
+  ** If your geospatial field type does not match your Elasticsearch mapping, click the *Refresh* button to refresh the field list from Elasticsearch.
+* Index patterns with thousands of fields can exceed the default maximum payload size.
+Increase <<settings, `server.maxPayloadBytes`>> for large index patterns.
+
 [float]
 ==== Features are not displayed