Kibana mapping conflicts and Elasticsearch mapping conflicts are not the same.

Elasticsearch Mapping Conflicts

Elasticsearch mappings are built from the Elasticsearch templates, for fields that don't have settings specified in the templates, the mappings are created dynamically from the data you send in. A mapping conflict occurs when you try to send data into a field that already has a mapping created but the data doesn't meet the same type (date, integer, string, etc.)

Kibana Mapping Conflicts

Kibana mapping conflicts occur when the fields don't match the type saved in the index pattern. This can be fixed by updating the index pattern field list.
This can be found in 

Kibana >> Management >> Index patterns. 

Then click on the rotating arrows in the top right corner. 

Logstash index pattern field list

What's next?

Did this answer your question?