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

geoip processor should be ECS compliant by default #48738

Open
martijnvg opened this issue Oct 31, 2019 · 2 comments
Open

geoip processor should be ECS compliant by default #48738

martijnvg opened this issue Oct 31, 2019 · 2 comments
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@martijnvg
Copy link
Member

As reported in #48715, the geoip processor should follow the field naming according ECS.
For example asn should be stored in asn.number field and organization_name should be stored in asn.organization.name field. We should also check for other fields. This field names are configurable, so it is not really problematic, but it would be better if by default ECS complaint field names are used.

@martijnvg martijnvg added >enhancement :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP labels Oct 31, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Ingest)

@philippkahr
Copy link
Contributor

Hi @martijnvg

I think we should also ping the beats guys on this. They have a workaround in their beats such as filebeat netflow module to rename the fields correctly:

- geoip:
        database_file: GeoLite2-ASN.mmdb
        field: destination.ip
        target_field: destination.as
        properties:
            - asn
            - organization_name
        ignore_missing: true
 - rename:
       field: source.as.asn
       target_field: source.as.number
       ignore_missing: true

https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/netflow/log/ingest/pipeline.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

4 participants