Thanks for you reply.
But this did not work for me. Can you tell me if the following is supposed to work or am I missing something?
We use docker/kubernetes. Instead of rebuilding the entire binary, i adjusted the Dockerfile as follows to include the modified "nginx/access/ingest/default.json" where i removed all references to geoip processor.
cat docker/Dockerfile
FROM docker.elastic.co/beats/filebeat-oss:7.4.1
COPY fields.yml /usr/share/filebeat/fields.yml
COPY module/nginx/access/ingest/default.json
/usr/share/filebeat/module/nginx/access/ingest/default.json #Added this line
USER root
With this docker image, I checked the running pod and the ingest file does not the geoip references.
But it did not work.
Appreciate your help. Sorry could not reply to you earlier.
did you build filebeat-oss from the source code?
Not I did not build the entire filebeat-oss from source code. But as I mentioned earlier, I made sure that the "module/nginx/access/ingest/default.json" that is used by filebeat does not have any references to "geo-ip". I did that by including this modified default.json into my own dockerfile/build.
My question is,
Is it necessary to rebuilt filebeat-oss ? Is the nginx ingest/default.json not read from the file by filebeat at startup. ?
Sorry I just came back from vacation. I think the way you are doing will work. But there are more than nginx module is using geoip and I believe all the modules that uses geoip needs to have a new/updated default.json file. Maybe give that a try?
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.