jjethwa / rundeck

GNU General Public License v3.0
123 stars 136 forks source link

Rundeck service.log to stdout #209

Closed venkatashreevaatsava closed 2 weeks ago

venkatashreevaatsava commented 1 year ago

Hi Team,

We are currently running rundeck in EKS and running successfully. We could not read logs using kubectl logs -f and logs are of docker logs not rundeck service.log.. currently we are SSH in to the pod and verifying logs. We need to see logs from rundeck using kubectl logs -f by default.

Kindly help

jjethwa commented 1 year ago

Hi @venkatashreevaatsava

That's the default behaviour as set up in log4j2 (reference: https://docs.rundeck.com/docs/administration/maintenance/logs.html#streaming-log-plugins ). As soon as the logging service starts up, STDOUT is redirected to the service.log. You could take a look at your log4j2.properties and modify it, but that could output a lot of data to your docker logs, so I wouldn't really recommend it 😄

venkatashreevaatsava commented 1 year ago

can you please explain what modification required in log4j.properties

jjethwa commented 1 year ago

Hey @venkatashreevaatsava

Sorry, I'm not an expert in log4j2. I really don't recommend doing it as you're going to put 100MBs or GBs in your docker logs. Most people would export the logs to something like splunk.

jjethwa commented 2 weeks ago

Closing as no more updates