for-aws icon indicating copy to clipboard operation
for-aws copied to clipboard

Would be useful to have docker engine logs available in CloudWatch Logs

Open hairyhenderson opened this issue 8 years ago • 7 comments

Expected behavior

I'd like to be able to view engine logs in CloudWatch Logs so that I can review them in a central location, and after nodes have terminated.

Actual behavior

I can't 😉

Information

The quick & dirty way would be doing a tail -F /var/log/docker.log in a container, since all container logs go to CloudWatch Logs, but it may be beneficial to not run this in a container, so we can diagnose issues when the Docker engine isn't running!

hairyhenderson avatar Jul 20 '17 15:07 hairyhenderson

Use the awslogs logging driver. https://docs.docker.com/engine/admin/logging/awslogs/

Deepak-Vohra avatar Jul 27 '17 18:07 Deepak-Vohra

awslogs is good for containers, which is enabled by default in D4AWS. But it is not enabled for the docker engine logs.

seriousben avatar Jul 27 '17 19:07 seriousben

any updates here ?

netflash avatar Sep 21 '17 18:09 netflash

@kencochrane @FrenchBen @friism - any possibility this could make it for 17.09?

hairyhenderson avatar Sep 21 '17 21:09 hairyhenderson

For those with interest with logs uploaded to CloudWatch, has anyone played with mounting the logs in a container with a setup similar to: https://hub.docker.com/r/mobingi/alm-awslogs/

FrenchBen avatar Oct 23 '17 17:10 FrenchBen

It's been a while, what workarounds/alternatives are people using?

molexx avatar Apr 23 '19 12:04 molexx

@molexx one possibility is to use something like filebeat to simply spit the logs to stdout and hence get them sent to CloudWatch Logs

hairyhenderson avatar Apr 23 '19 12:04 hairyhenderson