The latest News and Information on Log Management, Log Analytics and related technologies.
Friday, August 2, marked the second beta release for Loki, a long overdue version 0.2.0. Why did it take so long? In large part this was my fault. Having done some work to create a release process for version 0.1.0, I found myself focusing on other things, so improving that process ended up on the backburner. This entire time, in the back of my mind, I was delaying a new release until I could improve that process.
Developer teams and even operational teams often ignore monitoring applications. Deadlines, inexperience, company culture, and management can lead to poor or neglected monitoring inside developing platforms. Automating all monitoring tasks is an excellent way to avoid this scenario. Automation leads to lower costs, less time spent solving issues, and more efficient teams.
In our last post, we covered CloudWatch Metrics in a great deal of detail. We looked at how we can use it to monitor the health of our Lambda functions, including setting up service dashboards as well as alerts. In this post, we will focus on its sister service – CloudWatch Logs. We’ll see how it works and how to get the most out of it.
