We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When testing filebeat 7.10.0 on AWS vpcflow, i noticed some parsing errors when aws.vpcflow.log_status is NODATA or SKIPDATA
aws.vpcflow.log_status
NODATA
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: '-'
The text was updated successfully, but these errors were encountered:
Pinging @elastic/integrations-platforms (Team:Platforms)
Sorry, something went wrong.
kaiyan-sheng
Successfully merging a pull request may close this issue.
When testing filebeat 7.10.0 on AWS vpcflow, i noticed some parsing errors when
aws.vpcflow.log_status
isNODATA
orSKIPDATA
With those status, the log line looks like the following:
It generates mapping errors:
The text was updated successfully, but these errors were encountered: