[panw] Drop malformed messages from syslog processor - #16949
Merged
Conversation
In cases where a malformed syslog message is received, drop the message, since it likely won't contain enough data to parse properly, and will cause futher errors in the ingest pipeline and the document which would be stored.
Change the drop_event condition to drop the event when error.message is set AND log.syslog.priority is absent. This would indicate that the syslog message was not parsed properly, and the origin of the error message is in the syslog processor.
mjwolf
added
bugfix
mjwolf
marked this pull request as ready for review
January 15, 2026 19:31
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
mjwolf
enabled auto-merge (squash)
January 15, 2026 19:35
Contributor
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
cc @mjwolf |
taylor-swanson
approved these changes
Jan 15, 2026
Contributor
|
Package panw - 5.4.1 containing this change is available at https://epr.elastic.co/package/panw/5.4.1/ |
jakubgalecki0
pushed a commit
to jakubgalecki0/integrations
that referenced
this pull request
Feb 19, 2026
In panw, drop events where the syslog processor could not parse a syslog message from the event. This behaviour is the same as the TCP syslog parser, which will also drop unparsable syslog messages. The drop_event condition is "error.message" is set and "log.syslog.priority" is absent, which should indicate the syslog processor is the source of the error, because the mandatory syslog field is not present, and not drop events where an earlier processor is the cause of the error.
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
4 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
In panw, drop events where the syslog processor could not parse a syslog message from the event. This behaviour is the same as the TCP syslog parser, which will also drop unparsable syslog messages.
The drop_event condition is "error.message" is set and "log.syslog.priority" is absent, which should indicate the syslog processor is the source of the error, because the mandatory syslog field is not present, and not drop events where an earlier processor is the cause of the error.
Checklist
changelog.ymlfile.