-
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
[Filebeat] Dissect Parsing Error with Sophos Module #24237
Comments
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I don't think that this is because of separator behaviour. There are a collection of space-separated tokens in your log line that do not have a field split pattern; 'Feb', '11', '13:12:45', '_gateway' and '(0x0000)'. Looking on the Sophos Community forum the 'ether_type' field always appears to be quoted which solves the last token. Removing the syslog date and the _gateway token, and quoting the hex value to the 'Unknown' prefix allows the parse to succeed, although the test subsequently fails due to unrecognised fields; 'sophos.xg.in_display_interface', 'sophos.xg.out_display_interface', 'sophos.xg.ether_type', 'sophos.xg.nat_rule_id'. These fields appear in Sophos Community forum posts so probably they should be added. Altered log line (fictitious values added):
Resulting document:
|
For confirmed bugs, please report:
Hi, everyone
I have found a dissect parsing error by using Sophos module module of Filebeat 7.9.2.
The Sophos version is SFOS 18.0.4 MR-4 XG210
Here you are a log example:
The dissect error is the following:
KV in Ingest Node Pipeline does not have the same behaviour like Logstash. When it encounters
="
does not match=
as value separator.If I add before a gsub, it works. However, I am not aware of this change may affect to Sophos Pipeline in another section of the pipeline.
Thanks in advance,
Rodrigo
The text was updated successfully, but these errors were encountered: