Mapping conflict! A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.
Hi @AadarshKumayan,
I understand you get this message from Kibana, could you care to explain your setup? I'm specially interested in the list of projects you are using, along with their versions
i am using
elasticsearch -2.4.5
logstash-2.2.4-1.noarch
kibana - 4.4.2
json templates -
filebeat
topbeat
packetbeat
i installed elk a few days back so i am pretty sure i have been runnning the latest version
my elk server is running on centos vm
my client machine is ubuntu vm
kibana is showing error in packetbeat template
here is my sample packetbeat template
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.