Regenerate Filebeat golden files to account for Elasticsearch 7.13

[adriansr]

No description provided.

[botelastic]

This pull request doesn't have a Team:<team> label.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #25147 updated

• Start Time: 2021-04-19T17:00:22.716+0000

• Duration: 68 min 13 sec

• Commit: 73f20bb

Test stats 🧪

Test	Results
Failed	0
Passed	13531
Skipped	2271
Total	15802

Trends 🧪

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	13531
Skipped	2271
Total	15802

[andrewkroh]

This looks like a big change to the expected values. It's very likely to affect users that are filtering or alerting on AS org names. Do we have any idea if this is a change caused by something in Elasticsearch code or if it's something that MaxMind changed?

@probakowski Would you happen to have any insight? (saw you on a bunch of geoip related PRs)

[probakowski]

All changes for *.geo.* fields are for sure connected with GeoIPv2 project that finished recently. We haven't updated MaxMind databases for a long time (end of 2019?) due to license change and now we do update them to the latest released by MaxMind every 3 days (we still ship old databases but right after cluster start this new component kicks in and downloads new files)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b regenerate_7.13_golden_files upstream/regenerate_7.13_golden_files
git merge upstream/master
git push upstream regenerate_7.13_golden_files

[adriansr]

#25141 already addressed this issues. Closing.