Welcome to Part 2 of the “Concise guide to Loki,” a multi-part series where I cover some of the most important topics around our favorite logging database: Grafana Loki. As I reflect on the fifth anniversary of Loki, it felt like a good opportunity to summarize some of the important parts of how it works, how it’s built, how to run it, etc. And as the name of the series suggests, I’m doing it as concisely as I can.
If you ask us to score 2023, we would give it a 10 out of 10. Not only because we released Grafana 10 and celebrated the 10-year anniversary of the Grafana project with the first-ever Golden Grot Awards and the launch of a four-part documentary series.
If you’ve landed on this blog, you’re likely either considering starting your OpenTelemetry journey or you are well on your way. As OpenTelemetry adoption has grown, not only within the observability community but also internally at Grafana Labs and among our users, we frequently get requests around how to best implement an OpenTelemetry strategy.
Incidents almost never happen in a vacuum. When you receive an alert about a potential issue, odds are pretty good that you’ll need to navigate between different tools and teams to get things resolved. Of course, timing is critical in these situations, so the easier it is to communicate — between both tools and teams — the better off you’ll be.
How do you know that your open source project has been enthusiastically adopted by the community? A) Engineers give you a raucous standing ovation when a feature is revealed. B) People form a long line to meet you at an industry event. C) Every time there is a release, social media notifications blow up your phone. If you’re Grafana founder Torkel Ödegaard, the answer is D) all of the above.
Five years ago today, Grafana Loki was introduced to the world on the KubeconNA 2018 stage when David Kaltschmidt, now a Senior Director of Engineering at Grafana Labs, clicked the button to make the Loki repo public live in front of the sold-out crowd. At the time, Loki was a prototype: We bolted together Grafana as a UI, Cortex internals, and Prometheus labels to find out if there was a need for a new open source tool to manage logs.
With the release of Grafana 10.2, we made a number of enhancements to Grafana Alerting. These updates included the rollout of Insights, a new section of the Grafana Alerting home page. Available now to all Grafana Cloud users, Insights offers valuable information, such as statistics on alert rules and notifications, to help you monitor alerting data and quickly analyze alert performance.
In observability, finding the root cause of a problem is sometimes likened to finding a needle in a haystack. Considering that the problem might be visible in only a tiny fraction of millions or billions of individual traces, the task of reviewing enough traces to find the right one is daunting and often ends in failure.
This blog post by Grafana Labs Senior Software Engineer Milan Plžík was originally published on the Kubernetes.io blog on Nov. 16, 2023. There’s been quite a lot of posts suggesting that not using Kubernetes resource limits might be a fairly useful thing (for example, For the Love of God, Stop Using CPU Limits on Kubernetes or Kubernetes: Make your services faster by removing CPU limits ).
On Dec. 5, 2013, Torkel Ödegaard made the first commit in GitHub for a personal project that would become Grafana. “It’s hard to believe it’s been 10 years since Torkel launched Grafana, growing from a small man with a big dream to becoming the most popular data visualization software in the world,” says Grafana Labs co-founder and CEO Raj Dutt. “The Story of Grafana” chronicles that meteoric journey.
