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

Add property to GeoIp processor continent_code. #85820

Closed
jhaos opened this issue Apr 12, 2022 · 1 comment · Fixed by #108780
Closed

Add property to GeoIp processor continent_code. #85820

jhaos opened this issue Apr 12, 2022 · 1 comment · Fixed by #108780
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@jhaos
Copy link

jhaos commented Apr 12, 2022

Description

Hi, I'm currently using in my environment for ingestion filebeat>logstash>Elasticsearch, in order to reduce the resources we are going to take out Logstash and start using Filebeat instead directly to ingest the data to Elasticsearch.

I'm using the field continent_code and made several dashboards since Logstash allows it, check https://www.elastic.co/guide/en/logstash/current/plugins-filters-geoip.html, but checking the documentation to use an Elasticsearch processor there is no continent_code field, check https://www.elastic.co/guide/en/elasticsearch/reference/current/geoip-processor.html, but continent_name which I'm are not using in the template nor in the already ingested alerts.

Asking in the community channel I couldn't find any alternatives and one user suggested opening a feature request https://elasticstack.slack.com/archives/CNEDGGJQ3/p1649742148197329

The alternative would be to rename the field property in the template or delete it, but in any case, I will have to reindex all the data to adapt to the new fields and modify the dashboards that currently are using continent_code, and change to continent_name which is a tough task when several environments are involved with this kind of dashboards.

I would be appreciated, if possible, having this feature as soon as you can add it if you decide to.

Thanks in advance.

@jhaos jhaos added >enhancement needs:triage Requires assignment of a team area label labels Apr 12, 2022
@mayya-sharipova mayya-sharipova added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Apr 12, 2022
@elasticmachine elasticmachine added the Team:Data Management Meta label for data/management team label Apr 12, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@mayya-sharipova mayya-sharipova removed the needs:triage Requires assignment of a team area label label Apr 12, 2022
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

Successfully merging a pull request may close this issue.

3 participants