At first glance, microservices logging may seem simple. You just take the same principles you’ve always followed for monoliths and apply them to each microservice in your application, right? Well, no. The differences between microservices and monolithic architecture amount to much more than a difference in the number of services involved.
Managing stateful applications has been challenging for engineering and operations teams long before the debut of Kubernetes. In this post, we’ll explore all aspects of your deployments of stateful applications on Kubernetes, from the underlying hardware to Pod update strategies, and provide insights into how LogDNA uses stateful Kubernetes to build one of the world’s fastest log management platforms.
If you’re like me, you’re working from home, social distancing, and staying safe during these unprecedented times. I spend a lot of time thinking about how this will impact the way we will work in the future. Going through this with our teams creates stronger bonds as we learn how to work remotely and through a global pandemic. We now spend more time in zoom meetings and use more collaborative tools than we did even just a month ago.
We are so excited to announce that LogDNA received the IBM Cloud Embed Excellence Award during the IBM Think conference on May 5, 2020. IBM Cloud’s Data & AI Excellence Awards recognize the stellar performance of IBM Business Partners who drive extraordinary client experiences and business growth. IBM Log Analysis with LogDNA and IBM Cloud Activity Tracker with LogDNA are built on IKS and are deeply integrated with IBM Cloud.
On the internet, nothing necessarily stays easy, simple, and reliable forever – but we’re trying to keep it that way for your logs. When our customers use Kubernetes, they want to remain focused on the real challenges of scaling, and avoid infrastructure headaches, so that they can adapt to the unexpected easily and with a minimum of toil. That’s why we continue to invest in the LogDNA Agent. It’s built to handle file logging in even the most intensive Kubernetes deployments.
LogDNA is adding the ability to store and view raw lines, allowing customers to debug with logs in their unaltered form. If you’ve ever looked at your logs and noticed that the timestamp was different than what you expected, it is usually due to a long latency between the event and processing time of the logs. Depending on the size of the latency, we may update the log timestamp to order them accurately and to provide a cleaner and more intuitive search experience.
