-
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…
-
Read more about these RFCs.
-
The syslog parser adds the hostname to the message field when parsing RFC 3164 messages. Hostname gets correctly set in the source field.
## Expected Behavior
Full message: `Jan 1 12:15:00 nas.ex…
-
Hello. The generated Message Sender:
UdpSyslogMessageSender messageSender = new UdpSyslogMessageSender();
messageSender.setDefaultMessageHostname("myhostname"); // some syslog cloud s…
-
Hi,
What are your thoughts on changing the syslog parser to either accept a timezone parameter or defaulting timezone to Local? Right now the RFC 3164 parser's timezone is hardcoded to UTC, and tha…
-
### Component
systemd-journald
### Is your feature request related to a problem? Please describe
At the moment, when configuring `ForwardToSyslog = yes`, `systemd-journald` uses the UNIX socket dom…
-
### Go version
go version go1.22.1 linux/amd64
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH=…
svent updated
5 months ago
-
Hi,
i noticed that the host field in the visual syslog server GUI is not updated with the hostname of the machine sending the syslog message
-
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, `nontran…
-
I really wonder why rconsole enforces 1024 bytes restriction on message length while syslog no longer enforces this. There was a restriction on syslog message length introduced in RFC 3164(2001), but …
ghost updated
8 years ago