-
Notifications
You must be signed in to change notification settings - Fork 0
GPII-3394: Use logfile for logging #1
Conversation
syslog is not generally available inside a container.
# Enable logging with logfile as syslog is not generally available inside a container. | ||
<Plugin "logfile"> | ||
LogLevel "info" | ||
File "/var/log/collectd.log" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this log into stdout/stderr instead? Looks like it is possible using the same logfile plugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for stdout (but I don't have a good understanding of context here)
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
# Enable logging with logfile as syslog is not generally available inside a container. | ||
<Plugin "logfile"> | ||
LogLevel "info" | ||
File "/var/log/collectd.log" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for stdout (but I don't have a good understanding of context here)
30667d5
to
e26f6df
Compare
Using stdout is a good idea. However, I tried it and it didn't work -- no logs in The good news is run-agent.sh tails /var/log/collectd.log, so as-is we do see logs in |
Proposed to upstream as wikiwi#3 |
syslog is not generally available inside a container.
This also makes a whitespace-only, documentation-only change that causes the example DaemonSet to break :).
This PR is essentially a bugfix for upstream. I will PR it there after review here.