At Grafana Labs, we spend a lot of time talking to our customers, and something we’ve heard from people in a wide range of organizations is that they want to be able to better manage sudden spikes in cardinality. Here we will give you a basic overview of what cardinality is and why it’s an important factor in your observability setup, especially when there is a dramatic uptick.
Are your metrics, logs, and traces playing hard to get in your current observability setup? Feel like your on-call messages are left on read? Is the heatmap between your data sources fizzling out on your dashboard?
Do you actually know what your customers are looking for? A way to uncover new business opportunities is to analyze your system, collect what you really need, and visualize it through a comprehensive graph! Log traces are a great place to start because they usually contain useful information on your customers' interests. You just need to transform them.
Bram Vogelaar is a DevOps Cloud Engineer at The Factory, and he recently delivered an intro to observability talk during our Grafana Labs' EMEA meetup. When I talk to customers, they might tell me about how their applications are running in two data centers, but when we probe a little further, it turns out that their observability stack is only available in one of them. This revelation hit close to home last March.
The number of internet-connected assets around us that are powering services and utilities in a wide array of sectors is rising at an exponential rate. As a result, it’s becoming critical for businesses that provide such services and utilities to have an observability stack tailored to the type of physical hardware devices that are generally deployed in swarms.
The term “off-label” is used to describe when a product is being used successfully for something other than its intended purpose. It’s a quite common occurrence in the pharmaceutical industry, but it can also happen in the world of software. Grafana Loki was written as — and is marketed as — a simple, Prometheus-friendly logging backend with a very low total cost of ownership.
In September 2021, the U.S. Department of Defense’s Iron Bank formally authorized Grafana, Grafana Enterprise, and Grafana Loki, allowing the 100,000 employees and contractors who work on DoD software, both classified and unclassified, to easily select and immediately deploy Grafana Labs software without additional approvals and security certifications. In our first-ever government session at ObservabilityCon 2021, former U.S.
If you’re even the slightest bit familiar with how Grafana dashboards work, you’ve probably realized that the time range selector is one of the most important features. After all, when you’re using Grafana to visualize time series and logs, defining a time range is required for metrics and logs queries.
A huge challenge when dealing with incidents is the coordination and communication needed to put things right. What’s happened so far? Who has tried what query? Did we remember to keep stakeholders informed? What is the severity of the incident? Does this affect customers? Figuring this out requires a lot of back and forth as new team members join the incident.
Today we’re announcing the general availability of Grafana OnCall on Grafana Cloud for all paid and free plans. A big part of delivering great software is ensuring the right people get the right information when the inevitable incidents occur. We want to help you do that with Grafana OnCall, an easy-to-use, developer-first on-call management tool that’s built on top of the Grafana stack you know and love.
