Winlogbeat-* index has geoip.location as number
Using the guide https://www.elastic.co/blog/monitoring-windows-logons-with-winlogbeat
geoip.location was empty when examining event logs 4624.
After following the instructions in the guide geoip.location was populated with information, but geo_point was not referenced to geoip.location
filebeat-* index has geoip.location as geo_point but the map will not displat any geo_points - just a map with a red dot.
Used the guide https://www.elastic.co/blog/geoip-in-the-elastic-stack to setup filebeat.
My map:
I'm afraid I can't follow you there. geo_point is the data type used for the geoip.location field in the blog post you linked. Could you maybe rephrase the problem statement?
As for the Filebeat problem: Have you made certain that there are documents that are within the time interval selected in the time picker (if your index is configured as a time-based index)? Using the small upwards-pointing arrow in the lower left corner of the map you can show the raw data underlying the visualization as well details about the request, which might help your while debugging.
I can understand why you can't follow me, becaust I don't know what I am doing. I have been reading a lot, but most of what I am reading doesn't make much sense. So I will try to explain better.
I used the guide GeoIP in the Elastic Stack - Elasticsearch, Logstash, Ingest API | Elastic Blog to setup filebeat.
Firts part of my map.
Did you click the button at the top to apply the geo hash aggregation? The request and response show no indication that a geohash aggregation has been applied.
Thanks, I now know what to look for in the Response tab. Apparently the Apply Block in the Youtube videos has been changed to the button at the top.
Thanks again.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.