-
### A note for the community
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to …
-
### What happened?
```
A relay
will add a TIMESTAMP and SHOULD add a HOSTNAME as follows and will
treat the entire received packet after the PRI part from the original
packet as the …
-
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 it can't find a PRI value…
-
I'd like to use this container as a bridge to send only rfc5424 to telegraf (influxdb) container.
Is it possible? In the environment I only see I can specify the host and the port but not the forma…
-
Parser created as follows:
```go
p := rfc3164.NewParser(
rfc3164.WithYear(rfc3164.Year{YYYY: 2020}),
rfc3164.WithRFC3339(),
)
```
Example input:
```
Mar 1 09:38:48 myhost mya…
-
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…
-
Pipelines should support both RFC3164 and RFC5424 formats
-
Hi
echo "a" | /usr/lib/lognorm/lognormalizer -r a.rb
Segmentation fault (core dumped)
File a.rb:
version=2
#foo
type=@rfc3164pri:
type=@rfc3164header:%date:date-rfc316…
-
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…
-
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 …