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
The VPC Flow ingest pipeline added a fail processor for records whose token count does not match supported layouts and where parsing did not populate aws.vpcflow.srcaddr.
This changed behavior from silently indexing unsupported formats unparsed to surfacing them as pipeline errors.
fail on ctx?._temp_?.message_token_count != null && ctx?.aws?.vpcflow?.srcaddr == null
message: Unsupported VPC Flow Log format... Use a custom ingest pipeline to parse this format.
packages/aws/changelog.yml:12-16 documents this as version 6.16.0 behavior change.
Documentation impact:
packages/aws/docs/vpcflow.md documents supported formats (:51-62) and states only that Parquet is unsupported (:86), but does not explain the new unsupported plain-text failure behavior.
Users now need explicit guidance that unsupported plain-text formats generate pipeline_error events and that custom ingest pipelines are required for those layouts.
Suggested Actions
Update packages/aws/docs/vpcflow.md to document that unsupported plain-text VPC Flow layouts now trigger pipeline errors instead of being silently indexed.
Add a short troubleshooting note describing expected error behavior and recommending custom ingest pipelines for unsupported formats.
If applicable, add an example of an unsupported custom layout symptom (pipeline_error with unsupported format message) so users can recognize this condition quickly.
Note
🔒 Integrity filter blocked 37 items
The following items were blocked because they don't meet the GitHub integrity level.
#18066search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18164search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19124search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18498search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#17506search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19140search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18671search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19034search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19061search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18621search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18746search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18955search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18944search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18765search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18951search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18417search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
... and 21 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
Recent code changes in the repository have introduced documentation drift. The following change needs a corresponding documentation update.
Changes Requiring Documentation Updates
1. AWS VPC Flow now emits pipeline errors for unsupported plain-text formats
Commit(s):
ddd75707f42fb6fbea02af51f4fec692f842b5a7What changed:
failprocessor for records whose token count does not match supported layouts and where parsing did not populateaws.vpcflow.srcaddr.Evidence:
packages/aws/data_stream/vpcflow/elasticsearch/ingest_pipeline/default.yml:72-77adds:failonctx?._temp_?.message_token_count != null && ctx?.aws?.vpcflow?.srcaddr == nullUnsupported VPC Flow Log format... Use a custom ingest pipeline to parse this format.packages/aws/changelog.yml:12-16documents this as version6.16.0behavior change.Documentation impact:
packages/aws/docs/vpcflow.mddocuments supported formats (:51-62) and states only that Parquet is unsupported (:86), but does not explain the new unsupported plain-text failure behavior.pipeline_errorevents and that custom ingest pipelines are required for those layouts.Suggested Actions
packages/aws/docs/vpcflow.mdto document that unsupported plain-text VPC Flow layouts now trigger pipeline errors instead of being silently indexed.pipeline_errorwith unsupported format message) so users can recognize this condition quickly.Note
🔒 Integrity filter blocked 37 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Docs Patrol
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.