Project

General

Profile

Actions

Task #7589

open

eve: deprecate syslog filetype for eve

Added by Jason Ish 3 months ago. Updated 16 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Related issues 5 (4 open1 closed)

Related to Suricata - Task #6849: brainstorm: should certain eve ouput types be removed (eg syslog)NewOISF DevActions
Related to Suricata - Task #6851: eve/syslog: stats message too long for many default configurationsNewOISF DevActions
Related to Suricata - Task #7590: eve: remove syslog filetypeNewOISF DevActions
Related to Suricata - Feature #2380: [discussion] deprecate: 'alert syslog' outputClosedOISF DevActions
Related to Suricata - Task #7234: syslog: remove standalone syslog outputNewOISF DevActions
Actions #1

Updated by Jason Ish 3 months ago

  • Target version changed from TBD to 8.0.0-beta1
Actions #2

Updated by Jason Ish 3 months ago

  • Related to Task #6849: brainstorm: should certain eve ouput types be removed (eg syslog) added
Actions #3

Updated by Jason Ish 3 months ago

  • Related to Task #6851: eve/syslog: stats message too long for many default configurations added
Actions #4

Updated by Jason Ish 3 months ago

  • Related to Task #7590: eve: remove syslog filetype added
Actions #5

Updated by Jason Ish 3 months ago

  • Tracker changed from Bug to Task
Actions #6

Updated by Victor Julien 3 months ago

  • Target version changed from 8.0.0-beta1 to 8.0.0-rc1
Actions #7

Updated by Philippe Antoine about 1 month ago

Is this about removing src/output-eve-syslog.c ?

Actions #8

Updated by Jason Ish 17 days ago

For 8 it would just mean marking it as deprecated. Removal would be 9. But I'm not so sure we should? I can't remember the recent discussion around this. Previously it was due to syslog message sizes, but I think modern Linux has much larger message sizes that should probably be retested.

Actions #9

Updated by Jason Ish 16 days ago

Some further tests on sizes. Modern Linux syslog no longer has short limits like 1k. Instead, it is serviced by systemd, at least on systemd Linux systems. I don't think we have to worry about the rest. My tests have shown that this method has a maximum message size of under 220000 bytes (but over 210000), and rsyslog is happy to consume it, provided you increase the maximum rsyslog message size which can be much larger than 220000 bytes.

Looking through my own events, I have one Suricata event that is 180856 bytes. This event contains payload, but it contains the base64 and printable versions of the payload, both disabled by default. So its a worst case and probably not typical of a deployment.

These modern syslog implementation are also happy to consume and parse JSON.

Actions #10

Updated by Jason Ish 16 days ago

  • Related to Feature #2380: [discussion] deprecate: 'alert syslog' output added
Actions #11

Updated by Jason Ish 16 days ago

  • Related to Task #7234: syslog: remove standalone syslog output added
Actions #12

Updated by Jason Ish 16 days ago

  • Target version changed from 8.0.0-rc1 to 9.0.0-beta1

Pushing to 9, and a decision should still be made. I think it could have its uses, but would be nice to know if anyone is actually using it.

Actions

Also available in: Atom PDF