-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
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
Cisco asa/ftd: Remove _temp_ fields on failure #18392
Cisco asa/ftd: Remove _temp_ fields on failure #18392
Conversation
The shared pipeline for Cisco ASA and FTD creates temporary fields under the _temp_ object. If a failure happens in the middle of the pipeline, all those fields would be indexed, causing the index mapping to grow too big. Fixes elastic#18391
Pinging @elastic/siem (Team:SIEM) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
jenkins, test this |
FYI @alakahakai since you've been migrating this module to the package manager. |
@andrewkroh ACK. Will update the integration |
The shared pipeline for Cisco ASA and FTD creates temporary fields under the _temp_ object. If a failure happens in the middle of the pipeline, all those fields would be indexed, causing the index mapping to grow too big. Fixes elastic#18391 (cherry picked from commit 3605c47)
The shared pipeline for Cisco ASA and FTD creates temporary fields under the _temp_ object. If a failure happens in the middle of the pipeline, all those fields would be indexed, causing the index mapping to grow too big. Fixes elastic#18391 (cherry picked from commit 3605c47)
The shared pipeline for Cisco ASA and FTD creates temporary fields under the _temp_ object. If a failure happens in the middle of the pipeline, all those fields would be indexed, causing the index mapping to grow too big. Fixes elastic#18391 (cherry picked from commit 3605c47)
…ic#18476) The shared pipeline for Cisco ASA and FTD creates temporary fields under the _temp_ object. If a failure happens in the middle of the pipeline, all those fields would be indexed, causing the index mapping to grow too big. Fixes elastic#18391 (cherry picked from commit 9c3faed)
What does this PR do?
Updates the shared cisco asa/ftd ingest pipeline to remove the fields under
_temp_
in the case of failure.Why is it important?
Not removing the temporary fields can cause the index mapping to grow too big.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Unfortunately I couldn't add a test because Filebeat module's tests don't allow documents that cause errors.
Tested it locally by adding a test file that would cause an error in the pipeline:
And confirmed that with the fix,
_temp_
fields are no longer part of the output document:while before this patch one would get some of them:
Related issues