When testing filebeat 7.10.0 on AWS vpcflow, i noticed some parsing errors when aws.vpcflow.log_status is NODATA or SKIPDATA
With those status, the log line looks like the following:
version vpc-id subnet-id instance-id interface-id account-id - - - - - - - - - - start end - - SKIPDATA
version vpc-id subnet-id instance-id interface-id account-id - - - - - - - - - - start end - - NODATA
It generates mapping errors:
failed to parse field [aws.vpcflow.pkt_srcaddr] of type [ip] in document with id '229a9b7009-000001896666'. Preview of field's value: '-'
When testing filebeat 7.10.0 on AWS vpcflow, i noticed some parsing errors when
aws.vpcflow.log_statusisNODATAorSKIPDATAWith those status, the log line looks like the following:
It generates mapping errors: