Operations | Monitoring | ITSM | DevOps | Cloud

In a previous article, we explained the importance of monitoring the performance of your servers. Keeping tabs on metrics such as CPU, memory, disk usage, uptime, network traffic and swap usage will help you gauge the general health of your environment as well as provide the context you need to troubleshoot and solve production issues.

Many online applications use a web server as the primary point of contact for their clients. At least 43% of those systems are running the Apache HTTP Server. If you’re responsible for one of those systems, you need to work with the Apache error log.

Akamai provides the Content Delivery Network (CDN) which is a highly-distributed platform of servers optimized to deliver contents including web and media applications. These networks enable applications to easily serve content from closer to their end users. Centralizing Akamai logs increases the ability to observe the end to end application and service delivery. LogDNA is proud to enable integration with Akamai to provide better observability and a unified view for our customers.

If you’re a software developer, then you understand how vital application logging is in software development and a critical part of logging is something called logging levels. Log entries generally contain essential information—such as a timestamp, a message, and sometimes additional stuff like an exception’s stack trace. Those pieces of information are useful because they allow someone reading the log entry to understand how the application behaved in production.

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.