Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

securityonion-elastic: check ingest geoip fields #1725

Closed
dougburks opened this issue Feb 21, 2020 · 2 comments
Closed

securityonion-elastic: check ingest geoip fields #1725

dougburks opened this issue Feb 21, 2020 · 2 comments
Assignees
Projects

Comments

@dougburks
Copy link
Contributor

@dougburks dougburks commented Feb 21, 2020

Looks like we might still be getting an extra geoip field from elasticsearch ingest node parsing: region_iso_code.

image

We do have a region_code field in our template, so if this is the same field, it may just need to be renamed.

https://www.elastic.co/guide/en/logstash/7.x/plugins-filters-geoip.html

@dougburks dougburks added this to To do in 16.04.6.5 via automation Feb 21, 2020
dougburks added a commit to Security-Onion-Solutions/securityonion-elastic that referenced this issue Mar 6, 2020
@dougburks dougburks moved this from To do to In progress in 16.04.6.5 Mar 6, 2020
@dougburks dougburks moved this from In progress to In Testing in 16.04.6.5 Mar 6, 2020
@dougburks dougburks self-assigned this Mar 9, 2020
@dougburks

This comment has been minimized.

Copy link
Contributor Author

@dougburks dougburks commented Mar 10, 2020

To test, please verify that Elasticsearch ingest node parsing now renames region_iso_code to region_code.

@dougburks dougburks moved this from In Testing to Tested in 16.04.6.5 Mar 18, 2020
@dougburks

This comment has been minimized.

@dougburks dougburks closed this Mar 18, 2020
16.04.6.5 automation moved this from Tested to Done Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
16.04.6.5
  
Done
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.