Operations | Monitoring | ITSM | DevOps | Cloud

Your dashboard shows a latency spike. To investigate it, you copy the query, open logs in a new tab, paste and modify the query, lose your dashboard filters, and repeat for traces. By the time you find the issue, you have 15 tabs open. Starting today, you can click any panel and investigate right there. All your filters and variables carry over. No more tab juggling.

When multiple teams use Grafana, it can start to feel a bit messy. Dashboards pile up, permissions become unclear, and teams accidentally overwrite each other’s work. To help you and your organization stay clear, collaborative, and secure, we recommend putting all users in a single Grafana Cloud stack and managing access with teams, roles, and folders. To illustrate this, I’ll share a hypothetical example of how you can put this into practice across three teams. Let’s dive in!

A year ago, we hit a wall. Our Grafana OSS releases were excruciating to execute. The process was confusing and hard to follow, security patches were non-trivial, and many engineering hours were lost to an overly manual process. We needed to move fast, cut through ambiguity, and pull in just the right people without waiting on roadmaps or org charts.

Since its launch in 2020, the Infinity data source for Grafana has become the go-to solution to seamlessly query and visualize data from JSON, CSV, XML, and GraphQL endpoints within Grafana. Allowing users to integrate diverse data formats via HTTP-based APIs, the Infinity data source has enabled a wide range of use cases within our community over the years — from visualizing cloud computing costs to popular Pokémon games.