Adds information on the interactions between ES' dynamic mapping feature and

Kibana, in particular the .kibana index, to resolve Issue #3499.
This commit is contained in:
Paul Echeverri 2015-05-28 11:26:02 -07:00
parent 33a51567c4
commit 46ee3abf2c
2 changed files with 28 additions and 0 deletions

View file

@ -45,6 +45,9 @@ Kibana 4 users also need access to the `.kibana` index so they can save and load
For more information, see {shield}/_shield_with_kibana_4.html#kibana4-roles[Configuring Roles for Kibana 4 Users] in
the Shield documentation.
TIP: See <<kibana-dynamic-mapping, Kibana and Elasticsearch Dynamic Mapping>> for important information on Kibana and
the dynamic mapping feature in Elasticsearch.
[float]
[[enabling-ssl]]
=== Enabling SSL

View file

@ -30,6 +30,31 @@ After installing, run Kibana from the install directory: `bin/kibana` (Linux/Mac
That's it! Kibana is now running on port 5601.
[float]
[[kibana-dynamic-mapping]]
==== Kibana and Elasticsearch Dynamic Mapping
By default, Elasticsearch enables {ref}/dynamic-mapping.html[dynamic mapping] for fields. Kibana needs dynamic mapping
to use fields in visualizations correctly, as well as to manage the `.kibana` index where saved searches,
visualizations, and dashboards are stored.
If your Elasticsearch use case requires you to disable dynamic mapping, you need to manually provide mappings for
fields that Kibana uses to create visualizations. You also need to manually enable dynamic mapping for the `.kibana`
index.
The following procedure assumes that the `.kibana` index does not already exist in Elasticsearch and that the
`index.mapper.dynamic` setting in `elasticsearch.yml` is set to `false`:
. Start Elasticsearch.
. Create the `.kibana` index with dynamic mapping enabled just for that index:
+
[source,shell]
PUT .kibana
{
"index.mapper.dynamic": true
}
+
. Start Kibana and navigate to the web UI and verify that there are no error messages related to dynamic mapping.
[float]
[[connect]]
=== Connect Kibana with Elasticsearch