The latest News and Information on Log Management, Log Analytics and related technologies.
Kafka and the ELK Stack — usually these two are part of the same architectural solution, Kafka acting as a buffer in front of Logstash to ensure resiliency. This article explores a different combination — using the ELK Stack to collect and analyze Kafka logs. As explained in a previous post, Kafka plays a key role in our architecture. As such, we’ve constructed a monitoring system to ensure data is flowing through the pipelines as expected.
Let’s start with the happy ending — after a long search, we managed to identify a Netty memory leak in one of our log listeners and were able to troubleshoot and fix the issue on time before the service crashed.
To quote the timeless Ren and Stimpy jingle, “everyone needs a log.” It’s true — everyone does need a log, especially developers. Despite the fact that no developer looks forward to combing through logs, they’re incredibly useful when unexpected performance issues, like one we recently had with file uploads, need some investigation.
In October of last year, I joined Sumo Logic to lead sales and go-to-market functions with the goal of successfully launching our newly established Japan region in Tokyo. The launch was highly received by our customers, partners, prospects and peers in the Japanese market and everyone walked away from the event optimistic about the future and hungry for more!
If you maintain a regular practice of keeping log data, you probably have an established way of observing event logs in real time or you do it by using batch processing. There are two ways you can monitor event logs: manually and automatically. By monitoring event logs, you can gain deeper insight into system metrics, localize process bottlenecks, and detect security vulnerabilities. What are some other advantages of event log monitoring, and how can you get the most out of it?
Many of our customers want a simple way to see how often an event happens. In the past, LogDNA’s graphing capabilities helped to fulfill this need, but it took you away from your current log context and often forced you to recall a specific query in order to reflect the correct graph. When you are troubleshooting with constantly changing queries, it can be cumbersome to do this. We are excited to announce Timeline, now available alongside your logs in the log viewer.
