We’re happy to announce that Cortex v1.0 has been released! The horizontally scalable, durable, and fast Prometheus implementation is now generally available for production use. At Grafana Labs, we’ve been using Cortex in production for almost three years, including to power the Prometheus backend for the Grafana Cloud managed logging and metrics platform.
Microservices and containers have taken the tech industry by storm. Kubernetes is one of the tools that has evolved to manage these new aspects of software development. It is an open-source system for automating deployment, scaling, and management of containerized applications. One of the biggest challenges that organizations face when adopting Kubernetes is performing monitoring tasks in this dynamic environment.
It has been a little over 2 months since 1.3.0 was released. We started prepping for the 1.4.0 release several weeks ago; however, when I was writing this very blog post for the release, we discovered some confusing stats from the new statistics objects (which we’ll talk about in a bit). After sorting that out, we played the usual game of, “Wait, don’t release yet!
As everyone knows, the Grafana project began with a goal to make the dashboarding experience better for everyone, and to make it easy to create beautiful and useful dashboards like this one. But as Andrej Ocenas, a full stack developer at Grafana Labs, said in a recent FOSDEM 2020 presentation, the company has bigger ambitions for Grafana than just being a beautiful dashboarding application. What Grafana Labs is really aiming to do now is make Grafana into a full observability platform.
Stop. Before you start adding KPIs to your brand new glass table, make sure you’ve done your homework on design principles.
Over the last few days, most of us have been getting to grips with this new, albeit temporary, norm of remote working. At SquaredUp, we’ve always been able to work like this as all of the tools we use day-to-day are SaaS products or hosted in Azure, but while we’ve always had the right tools, we’ve never actually had to experience everyone being out of the office at the same time.
Let Data Shed Some Light in the Midst of Uncertainty The burden the COVID-19 novel coronavirus has placed on the world is enormous. There’s a great thirst for information and clarity. So, we at Logz.io have decided to offer a Community COVID-19 Dashboard Project, so that everyone can better understand how the outbreak impacts the world and their region. We see that as a community effort.
Have you heard about using the hash ring in Loki and Cortex? Here is a short version: In Cortex and Loki, the ring is a space divided by tokens into smaller segments. Each segment belongs to a single “ingester” (component in Cortex and Loki that receives data) and is used to shard series/logs across multiple ingesters. In addition to the tokens, each ingester also has an entry with its ID, address, and the latest heartbeat timestamp updated periodically.
