Picture a perfect world where all logs shared the same layout, format, and structure. Every application, programming language, and logging framework created logs that were verbose, yet easily parsable. Of course, we don’t live in this ideal world, and so we’re stuck with dozens or even hundreds of various log formats. While LogDNA supports a large number of common log formats, there are formats out there that our automatic parsing engine won’t recognize.

We hope you’re enjoying your time at IBM Think 2019 – thank you for dropping by to chat with our team (at booth 598) and now checking our blog. As promised, setting up modern logging for your Kubernetes clusters on IBM Cloud is really easy and in this article we’ll take a closer log at IBM Log Analysis with LogDNA and how to use it to log your cloud Kubernetes clusters.

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.

There’s no shortage of providers willing to host your containers. Many of the world’s biggest cloud platforms offer Kubernetes as a service, including features such as automatic scalability and high availability. However, Google Cloud Platform (GCP) stands out as perhaps the best tool for building and hosting a Kubernetes cluster for a number of reasons. In this article, we’ll present these reasons and why GCP offers a better Kubernetes experience than other providers.

In a previous post, we explained the concept of configuration management and presented three of the most popular tools: Chef, Puppet, and Ansible. We also briefly explored the impact that containerization is having on configuration management, and how the two can be used in combination. This article takes a more in-depth look at this relationship by presenting different techniques for using Chef, Puppet, and Ansible to deploy and manage a Kubernetes cluster.

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.

One of the biggest software development shifts of the past decade has been the emergence of the DevOps movement. There is a growing demand for DevOps Engineers, and organizations that have embraced DevOps practices are becoming more efficient in iterating through service delivery.

Being proactive is one of the key elements of a successful company. We are always seeking ways to help you perform at your best. With this goal in mind, we have been working on enhancements over the past couple of months in our alerting logic. Today, we’re proud to announce another highly anticipated feature from LogDNA: Absence Alerting!

Configuration management is an essential process for DevOps teams. It allows engineers to manage dozens, hundreds, or even thousands of machines in a consistent and automated way. While there are many configuration management tools available, three of the most popular are Chef, Puppet, and Ansible. In this post, we’ll explain how these tools work and the unique benefits that they offer.