As Grafana has grown from a visualization platform to an observability solution, we’ve added many tools along the way. These tools are dedicated to help you throughout the software development life cycle, whether you are trying to prevent incidents, you are monitoring your application or infrastructure, or if you are in the middle of an incident.
We all know about the great things Grafana dashboards can do, and configuring them as code makes it possible to get even more out of them. These days, Grafana resources can mostly be managed as code in a declarative manner, which enables code review, code reuse, and in general, better workflows. This guide presents a few as code tools you can use to declaratively manage Grafana resources, plus some tips and tricks on how to incorporate them efficiently into your own use cases.
We recently announced a new open source project called Grafana Phlare. This highly available continuous profiling data source is built into Grafana core, allowing you to seamlessly monitor your profiling data. With continuous profiling, you can see which parts of your applications are consuming the most resources. You can then use that data to make any necessary tweaks to reduce consumption, which translates to lower costs.
Ricardo Liberato is a consultant building solutions for corporate clients using the power of the Grafana ecosystem to tackle problems beyond the data center and into the business realm. Since 2006, I’ve been consulting for a Fortune 100 life sciences company building increasingly powerful observability solutions. We started with custom-built solutions, migrating to Grafana and Prometheus back in the Grafana 3 days.
Grafana Loki 2.7 has arrived! With it comes an experimental feature we are rather excited about: a redesigned index based off of the Prometheus TSDB index. While we are still in the early stages, this enhancement in Grafana Loki, which we previewed at ObservabilityCON 2022, creates a smaller storage footprint, better query performance, and much more that we will dive into below!
The much-anticipated release of Grafana Tempo 2.0, which we previewed at ObservabilityCON 2022, will represent a huge step forward for the distributed tracing backend. Among the biggest highlights will be TraceQL, a first-of-its-kind query language that makes it easier than ever to find the exact trace you’re looking for. There’s supposed to be a video here, but for some reason there isn’t. Either we entered the id wrong (oops!), or Vimeo is down.
Welcome to Grafana 9.3! Get Grafana 9.3 In our continued efforts to make Grafana more accessible and easier to use, we are excited to showcase new updates to improve navigation, introduce localization, and much more. Read our What’s New documentation to learn all about the latest release and for more details, refer to the changelog.
Brazil’s Banco Itaú is the largest bank in Latin America, so when performance and uptime issues impact its applications, the reverberations can be massive. “It can impact the whole economy of Brazil. It can damage other banks’ business too,” Ana Paula Genari Martin, SRE manager at Banco Itaú, said in her recent ObservabilityCON talk. And keeping those applications running is no small feat, considering the size of their digital operations.
It’s hard to think of a use case that Grafana hasn’t been used for. When Torkel Ödegaard launched the Grafana open source project with his first commit in December 2013, “my goal was to make time series data accessible for a wider audience, to make it easier to build dashboards, and to make graphs and dashboards more interactive,” he said.
Until recently, Grafana Cloud users had to rely on API keys to read and write data to and from the composable observability platform. These API keys had minimal features, which limited administrators’ ability to manage account access on a granular level. We’re keenly aware of these shortcomings, and we’ve been working to overhaul and replace these API keys with something more flexible, more reliable, and more secure.
