Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[pfsense] switch from grok to syslog processor #3586

Closed
leehinman opened this issue Jun 24, 2022 · 1 comment · Fixed by #3612
Closed

[pfsense] switch from grok to syslog processor #3586

leehinman opened this issue Jun 24, 2022 · 1 comment · Fixed by #3612
Assignees
@kcreddy
Labels
enhancement New feature or request

Comments

@leehinman
Copy link
Contributor

We have reports of OPNsense logs that look like

<134>1 2022-06-09T14:44:11-06:00 OPNsense.example.com filterlog 76404 - [meta sequenceId="1"] 124,,,fae559338f65e11c53669fc3642c93c2,ixl1_vlan70,match,pass,out,4,0x0,,63,5687,0,DF,6,tcp,60,192.168.1.1,10.10.10.10,40370,80,0,S,3364871769,,65535,,mss;sackOK;TS;nop;wscale

The syslog header is different from what the grok currently expects. We should switch to the syslog processor once elastic/beats#31798 is merged. That will handle both syslog headers.
@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@kcreddy kcreddy self-assigned this Jun 27, 2022
@kcreddy kcreddy mentioned this issue Jun 28, 2022
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kcreddy kcreddy

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix pfsense grok to support new opensense log format kcreddy/integrations
3 participants
@kcreddy @elasticmachine @leehinman