aws/vpcflow: surface unsupported flow log formats as pipeline errors - #18899
Merged
Conversation
Records with a field count that does not match any known VPC Flow Log layout were silently indexed without parsed fields. Add a fail guard after the dissect branches so these records trigger the pipeline-level on_failure handler, setting event.kind to pipeline_error with a descriptive message. Custom ingest pipelines continue to run and can override the error for formats they handle. Closes elastic#18521
kcreddy
added
Integration:aws
kcreddy
commented
May 8, 2026
Comment on lines
+72
to
+77
| - fail: | ||
| if: ctx?._temp_?.message_token_count != null && ctx?.aws?.vpcflow?.srcaddr == null | ||
| message: >- | ||
| Unsupported VPC Flow Log format: record has {{{_temp_.message_token_count}}} fields, | ||
| which does not match any integration supported VPC flow log format. | ||
| Use a custom ingest pipeline to parse this format. |
Contributor
Author
There was a problem hiding this comment.
fail used here instead of terminate because terminate hides the problem, fail surfaces it.
kcreddy
marked this pull request as ready for review
May 8, 2026 13:47
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Contributor
Author
|
The CI is failing on an unrelated |
Contributor
Author
|
/test |
kcreddy
marked this pull request as draft
May 12, 2026 06:22
Contributor
Author
|
The CI error is due to the expired certificate on |
7 tasks
Contributor
Author
|
/test |
Contributor
🚀 Benchmarks reportTo see the full report comment with |
kcreddy
marked this pull request as ready for review
May 18, 2026 13:29
5 tasks
efd6
approved these changes
May 18, 2026
💚 Build Succeeded
History
cc @kcreddy |
Contributor
|
Package aws - 6.16.0 containing this change is available at https://epr.elastic.co/package/aws/6.16.0/ |
herrBez
pushed a commit
to herrBez/integrations
that referenced
this pull request
Jun 1, 2026
…lastic#18899) Records with a field count that does not match any known VPC Flow Log layout were silently indexed without parsed fields. Add a fail guard after the dissect branches so these records trigger the pipeline-level on_failure handler, setting event.kind to pipeline_error with a descriptive message. Custom ingest pipelines continue to run and can override the error for formats they handle. Closes elastic#18521
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.Related issues