You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearchteam is currently rewriting the GeoIP processor to store the as number as as.asn instead of being ECS compliant and storing it as as.number. As soon as this one is fixed, I think we should update all the pipelines? Every task is using ignore_missing: true so it is not a breaking change, however, deleting unnecessary code is always good.
The text was updated successfully, but these errors were encountered:
philippkahr
changed the title
Fix beats workaround for as number as soon as GeoIP processor is fixed in Elasticsearch
Fix beats workaround for as.number as soon as GeoIP processor is fixed in Elasticsearch
Nov 9, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the enhancement:
Elasticsearchteam is currently rewriting the GeoIP processor to store the
as number
asas.asn
instead of being ECS compliant and storing it asas.number
. As soon as this one is fixed, I think we should update all the pipelines? Every task is usingignore_missing: true
so it is not a breaking change, however, deleting unnecessary code is always good.elastic/elasticsearch#48738
I already took care of all filebeat modules.
The text was updated successfully, but these errors were encountered: