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
I mentioned this in our support Slack channel and was told to create a new issue to resurface #68.
We use the s3-logfile Terraform module to deploy the Honeycomb agentless-integrations-for-aws to send VPC flow logs to a dataset. The solution works great. Would it be possible to accommodate for more than the version 2 fields? Right now, the regex pattern is:
Including fields such as type (IPv4 or IPv6) and pkt-dst-aws-service (EC2, CLOUDFRONT, ROUTE53, etc.) would be helpful. The Terraform module does not include a way to specify custom regex.
The text was updated successfully, but these errors were encountered:
Also thanks for opening this idea, we'll take a look in-depth next week after the holiday. Do you have any interest in submitting a PR if we accept this idea?
I mentioned this in our support Slack channel and was told to create a new issue to resurface #68.
We use the s3-logfile Terraform module to deploy the Honeycomb agentless-integrations-for-aws to send VPC flow logs to a dataset. The solution works great. Would it be possible to accommodate for more than the version 2 fields? Right now, the regex pattern is:
Including fields such as type (IPv4 or IPv6) and pkt-dst-aws-service (EC2, CLOUDFRONT, ROUTE53, etc.) would be helpful. The Terraform module does not include a way to specify custom regex.
The text was updated successfully, but these errors were encountered: