logs format (when sent to udp port via syslog) #215
Replies: 3 comments 2 replies
-
nvm, looks like my problem was not the prepended header but rather a typo in the format I set for logs on nginx |
Beta Was this translation helpful? Give feedback.
-
I made sure that the nginx server running in the main container pod did actually stream the logs to the chosen port via udp, that was failling for some reason |
Beta Was this translation helpful? Give feedback.
-
my main container is just a hello-world kinda nginx server (non-root and I need to expose port 8080 but that's irrelevant here), in the docker image I have
and then I have this files/etc/nginx/override.conf
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying the exporter in a sidecar on kubernetes,
got the logs sent to the right port in the main container but syslog prepends a header that I am not able to remove
(syslog in my main container image is neither rsyslog nor syslog-ng, it's busybox syslogd)
which I think it's due to that...
I have set:
(tried also
format = "rfc3164"
there)should I try to modify the line
format = "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\""
in the configmap above to account for the header?Beta Was this translation helpful? Give feedback.
All reactions