For the last six months, the Acme Anvil Corporation has been migrating some of their bare metal infrastructure to Docker containers. After the initial implementation, the team has decided to implement a better logging strategy by using a centralized syslog server.
You have been tasked with configuring syslog on one of the Docker instances. Next, you will configure Docker to use syslog instead of the JSON file log. Finally, you will test the configuration by spinning up two containers to test logging with syslog and a JSON file.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Configure syslog.
You will need to open
rsyslog.confand make a few changes:vim /etc/rsyslog.confUncomment the two UDP syslog receptions:
#$ModLoad imudp #$UDPServerRun 514to
$ModLoad imudp $UDPServerRun 514- Configure Docker to use syslog.
Create the
daemon.jsonfile.mkdir /etc/docker vim /etc/docker/daemon.jsonAdd the following content.
{ "log-driver": "syslog", "log-opts": { "syslog-address": "udp://PRIVATE_IP:514" } }- Create a container using syslog.
Enable and start the Dockere service.
sudo systemctl enable docker sudo systemctl start dockerCreate a container called
syslog-loggingusing the httpd image.docker container run -d --name syslog-logging --log-driver none httpd- Create a container using a JSON file.
Create a container that uses the JSON file for logging.
docker container run -d --name json-logging --log-driver json-file httpd- Verify that the `syslog-logging` container is sending its logs to syslog.
Make sure that the
syslog-loggingcontainer is logging to syslog by checking the message log file:tail /var/log/messages- Verify that the `json-logging` container is sending its logs to the JSON file.
Execute
docker logsfor thejson-loggingcontainer.docker logs json-logging
