[PANW] Add conditional to processors populating _temp_ fields for internal and external zones #14671
Conversation
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
leandrojmp
changed the title
5 tasks
andrewkroh
added
Integration:panw
|
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
packages/panw/data_stream/panos/elasticsearch/ingest_pipeline/traffic.yml
Show resolved
Hide resolved
packages/panw/data_stream/panos/elasticsearch/ingest_pipeline/traffic.yml
Show resolved
Hide resolved
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
taylor-swanson
approved these changes
Jul 25, 2025
|
Package panw - 5.3.2 containing this change is available at https://epr.elastic.co/package/panw/5.3.2/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The first 2 processors in the logic to populate the field
network.directionrelies on the existence of the fields_conf.internal_zonesand_conf.external_zonesif the user does not configure those fields in the integration, or if the source data does not have this field, those processors would still try to process every message and would fail because the field does not exist, this can add some extra time in the overall processing time of the ingest pipeline.These 2 processors needs to be conditionally executed to avoid this, we detected this issue while troubleshooting the performance of the ingest pipeline.