The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
In any enterprise, IT or otherwise, infrastructure monitoring and management are extremely crucial. A drop in performance or a failure of a machine can lead to significant delays. For that reason, there’s a constant need for eyes on the overall infrastructure to ensure smooth operations. One of the best ways to gauge the overall health of infrastructure is by monitoring key performance indicators (KPI).
Monitoring is a critical aspect of cloud computing. At any time, you need to know what’s working, what isn’t, and have the ability to respond to changes occurring in a given environment. Effective monitoring begins with the ability to collect performance data from across an ecosystem and present it in a useful way. So the easier it is to manage monitoring data across an ecosystem, the more effective those monitoring solutions are and the more efficient that ecosystem is.
A new version of Loki was released back in November, and I’m here to talk about one of its most exciting features. Loki 2.4 finally removed the requirement that all data must be ingested in timestamp-ascending order. Instead, Loki now allows out of order logs up to a configurable validity window (more to come on that). In this post, I’ll walk through what all this means and why we’re thrilled about it.
