go-syslog icon indicating copy to clipboard operation
go-syslog copied to clipboard

Blazing fast syslog parser

Results 15 go-syslog issues
Sort by recently updated
recently updated
newest added

https://github.com/influxdata/go-syslog/blob/ac565dc76ba6bb17b47140fb74355d1de7f19307/rfc5424/builder.go#L64-L65 Those two variables are defined on the package level. That means that two independent `rfc5424.SyslogMessage` objects with structured data can't be built concurrently – race detector correctly reports unsynchronised...

Hello, We are trying to use go-syslog parser to parse syslogs for one of our system but our logs are in format as below: `Oct 11 22:14:15 su: 'su root'...

Would like to add support in rfc3164 message parse so that if messages have Year information, those messages are not rejected by syslog.

rfc3164 parser can parse log like `logStr = "Jul 16 02:15:13 an 200050021 id=OS time="2020-7-16 02:15:13" timezone=GMT(+0000)"`, but can't parse log like `logStr = "Jul 16 2020 02:15:13 an 200050021...

enhancement

I'm trying to parse messages from rsyslog's owfwd module. rsyslog uses BSD syslog messages (RFC 3164). However, the two parsers that can handle reading multiple syslog messages from a stream,...

When syslog is being saved to files, the PRI value is typically removed (I don't know real reason for that though, but it's just my observation). And go-syslog complains that...

enhancement
help wanted

Parser created as follows: ```go p := rfc3164.NewParser( rfc3164.WithYear(rfc3164.Year{YYYY: 2020}), rfc3164.WithRFC3339(), ) ``` Example input: ``` Mar 1 09:38:48 myhost myapp[12345]: foo [bar] baz ``` Output (take a look at...

bug
help wanted

Create a generic syslog parser able to automatically infer transparent framing technique from non-transparent ones. A significative quote from RFC6587. A transport receiver can assume that non-transparent-framing is used if...

following [this](https://github.com/influxdata/go-syslog/issues/30) issue. in the new standard (RFC [5424](https://www.rfc-editor.org/rfc/rfc5424#section-6.2.1)) it stated that 'Facility and Severity values are not normative but often used.' meaning that the pri header is not mandatory....