Introduction

Whenever something goes wrong with our running applications or service, the first thing we usually look for in our application logs is a clue as to what is causing the issue. So, it becomes important to understand how you'll be collecting logs and monitoring log events for your project.

As we implement a microservice architecture with Docker, it becomes more important to ensure we are able to see the logs our applications and containers are generating. As the number of containers and services grows, trying to access each running container individually becomes increasingly unwieldy as a means of troubleshooting any issues that arise. For scalable applications, where they scale up and down depending on demand, it may become increasingly difficult to track log errors across multiple containers.

Ensuring we have a proper log monitoring strategy in place will help us troubleshoot our applications and ensure our services are running at their optimum efficiency....