-
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 …
-
### What happened?
OTEL collector (contrib `v0.82.0`) logs errors from syslog receiver, when it receives Grafana syslog message:
```
2023-08-01T23:20:00.001Z error helper/transformer.go:99…
-
metalog seems to ignore syslog messages sent to /dev/log that satisfy the RFC.
Is there a doc on what kind of syntax does metalog actually expect?
l29ah updated
3 weeks ago
-
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…
-
### 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 …
-
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…
-
The default logging level for miniupnpd does not show add/delete/change logs for NAT and Firewall manipulations in the routing log file.
Form a security standpoint, this is highly undesirable. Secu…
-
- If the configuration specifies a UNIX domain socket, and this socket already exists in the filesystem, consumer.Syslogd will fail with `[2017-07-24 00:26:19 CEST] ERROR Failed to open unix:///tmp/go…
-
# Problem statement and example
Given a poorly formed, lazy, unconventional message:
```
Poor form RFC3164 without syslog header
```
pmrfc3164 (with `force.tagEndingByColon="on"`) will pars…