Sidehistorik
...
Kodeblok |
---|
"mapping":{"location":{"type":"geo_point"}} |
Advarsel | ||
---|---|---|
This is for sure because I use "filebeat" as index for apache logs, and not "logstash" as is default (if logstash ships directly to Elasticseach). The filebeat template in /etc/filebeat/filebeat.template.json has no geo/location mappings, and I am not sure its even used; as Elasticseach just creates the index upon getting data in.. In /etc/logstash/conf.d/10-beats-input.conf I do have:
but that seems to be "not enough" - possibly because I have no output template defined in /etc/logstash/conf.d/30-elasticsearch-output.conf |
....so we need to change this:
Tip |
---|
TBD... http://www.pipebug.com/elasticsearch-logstash-kibana-4-mapping-4.html |
Info |
---|
As a test, I changed the Logstash config, so the type=apache went into the Logstash index, and the Geomapping just worked... |