How to set hostname for remote syslog? #232
-
|
I'm poking around with homelabbing some stuff with a couple Gokrazy instances on my network and just got syslog-ng -> promtail -> loki setup. I noticed when pulling the logs that the gokrazy instances don't set the hostname. Is that a configuration issue or a missing feature at the moment? I figured the instance's configured |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
gokrazy does use the hostname in its remote syslog messages, at least on my devices. See this tcpdump packet capture (expression
The gokrazy syslog daemon separates log messages by host name, and I just now double-checked that my instance does indeed write to one logfile per hostname. I wonder if you’re hitting a syslog format incompatibility in some part of your stack? |
Beta Was this translation helpful? Give feedback.
-
|
Turns out the default option for |
Beta Was this translation helpful? Give feedback.
gokrazy does use the hostname in its remote syslog messages, at least on my devices. See this tcpdump packet capture (expression
port 514):The gokrazy syslog daemon separates log messages by host name, and I just now double-checked that my instance does indeed write to one logfile per hostname.
I wonder if you’re hitting a syslog format incompatibility in some part of your stack?