So based on that issue it looks like this is going to be picked up for the 7.17 release, so we should have this resolved here soon. Thanks for raising this and appreciate the patience here.
Thank you for referencing my thread about my similar question earlier. We noticed that on our map the Error loading map features has been fixed for somethings, but not others. Have all of your issues be resolved with the 7.17 update? It seems that the data coming from Elastic Agents is now works for us, while firewall logs that went through Logstash still have the old error.
I also had a problem loading the entire map. We detected that there was a very strict rule in the firewall for outgoing connections. We asked to adjust the rules more flexibly so that the map could reload all the information on the dashboard.
I don't think either of our firewall's rules are our issue, but I will keep looking in that direction. For the time being we created a dashboard with a custom map that shares all the source/destination geolocation data that didn't show in Security > Network.
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.