-
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 …
-
Continuing the work started in #3377
Address these firewall integrations to ensure each is consistent in the syslog formats supported.
**Fortinet**
Syslog configuration now includes the optio…
-
### Expected behavior
When converting from RFC5424 messages to RFC3164, the ending colon of the syslog tag could be appended for RFC3164, to help systems that expect the colon. The colon should be …
-
Pipelines should support both RFC3164 and RFC5424 formats
-
Create a new syslog codec to add support for [RFC3164](https://tools.ietf.org/html/rfc3164) and [RFC5424](https://tools.ietf.org/html/rfc5424) (with continued ISO8601 date format support) so it can be…
-
Hi, I think that both of following time strings are valid RFC3339 time format. However, RFC3164 parser is not able to parse the second type of timestamp (i.e. ```2019-11-06T08:12:25Z```) due to the ex…
-
We're getting a bit of junk when processing syslog lines from several applications that implement the old syslog format (RFC 3164) but are actually putting something in `[]` without key-value pairs.
…
-
# Problem statement and example
Given a poorly formed, lazy, unconventional message:
```
Poor form RFC3164 without syslog header
```
pmrfc3164 (with `force.tagEndingByColon="on"`) will pars…
-
specification here:
http://www.ietf.org/rfc/rfc3164.txt
section 4.1.3
Thanks!
-
The syslog acquisition modules tries to be a little bit too "smart" and reconstruct a RFC3164 syslog line based on what what read from the network.
But it fails often if your syslog messages are no…