# Grafana Labs

Recent content in Grafana Labs blog on Grafana Labs

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Bring charts, queries, and context into one shareable document: Introducing Grafana Notebooks

DevFeed: [Bring charts, queries, and context into one shareable document: Introducing Grafana Notebooks](<https://devfeed.tech/articles/bring-charts-queries-and-context-into-one-shareable-document-introducing-grafana-notebooks-145261.md>)

Original publisher: [Read original article](<https://grafana.com/blog/bring-charts-queries-and-context-into-one-shareable-document-introducing-grafana-notebooks/>)

Author: Daniel Moosdeen Mui

Published: 2026-11-19T15:22:49Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-work](<https://devfeed.tech/tags/ai-assisted-work.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [charts](<https://devfeed.tech/tags/charts.md>), [context](<https://devfeed.tech/tags/context.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [explore](<https://devfeed.tech/tags/explore.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [notebook](<https://devfeed.tech/tags/notebook.md>), [observability](<https://devfeed.tech/tags/observability.md>), [panel](<https://devfeed.tech/tags/panel.md>), [payment](<https://devfeed.tech/tags/payment.md>), [queries](<https://devfeed.tech/tags/queries.md>), [question](<https://devfeed.tech/tags/question.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [recommendation](<https://devfeed.tech/tags/recommendation.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [traces](<https://devfeed.tech/tags/traces.md>), [visualization](<https://devfeed.tech/tags/visualization.md>)

### AI overview

Grafana Notebooks provide a shareable working document for combining charts, Explore queries, Assistant visualizations, and written reasoning. Users can add a dashboard panel or Explore content to a new or existing notebook, refine the query without changing the source dashboard, set an absolute time range on a panel, and reorder blocks; edits save automatically. Assistant visualizations can be added from the side pane or Workspace, and the notebook's Assistant pane can help modify a visualization or refine the document. In the checkout example, evidence points to one provider's timeouts and a deployment change to its timeout setting; the notebook presents this as a suspected cause to test, not a confirmed conclusion. Teammates with access can inspect the analysis and queries, while testing occurs separately in the service's test environment. Notebooks are in public preview in Grafana Cloud and self-managed Grafana; self-managed setup requires enabling the `dashboard.notebooks` feature toggle. Cloud access is rolling out over the coming weeks. Comments and live editing are described as being explored.

### Source excerpt

A teammate asks why you think a deployment caused checkout failures. You have an error-rate chart in your dashboard, a query that narrows the failures to one payment provider, and an explanation you've been exploring with Grafana Assistant. To bring your teammate up to speed, you start collecting screenshots and query links, then write out how they connect. That explanation is part of the analysis. Your teammate needs to see what supports the conclusion and where you're still making an assumption. As findings come from both your own exploration in Grafana and from AI-assisted work, having one place to examine them together becomes key. Grafana Notebooks help you do just that, bringing charts, queries, and findings from Assistant together in one working document, so teammates can follow your reasoning and assess next steps. In this post, we'll use the checkout example above to show how this works in practice, then look at how Notebooks can support rollout decisions and post-incident reviews. How Notebooks work: develop your analysis in a working document Through conversations with users, we've heard a recurring need for a lightweight place to work through a question and share the results. Notebooks give that work room to develop inside Grafana, from an initial observation to a recommendation someone can assess. You can start with a panel you've already found. Select Add to notebook from its dashboard menu, or from the Add menu in Explore, and choose a new or existing notebook. Then add your explanation and reorder the blocks as the argument takes shape. Your edits save automatically. Assistant can contribute to your working document, too. Add a visualization generated in an Assistant conversation directly to a notebook, whether you're using the side pane or Workspace. Once you're in the notebook, open the Assistant side pane to ask for changes to a visualization or help refining the document. You can also edit the content directly as your analysis develops. Work thro

## Find the log line that matters faster with full-text search in Grafana Cloud Logs

DevFeed: [Find the log line that matters faster with full-text search in Grafana Cloud Logs](<https://devfeed.tech/articles/find-the-log-line-that-matters-faster-with-full-text-search-in-grafana-cloud-logs-139558.md>)

Original publisher: [Read original article](<https://grafana.com/blog/find-the-log-line-that-matters-faster-with-full-text-search-in-grafana-cloud-logs/>)

Author: Jason Nochlin

Published: 2026-11-17T16:53:32Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Cloud Logging](<https://devfeed.tech/topics/cloud-logging.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud-logs](<https://devfeed.tech/tags/grafana-cloud-logs.md>), [log-aggregation](<https://devfeed.tech/tags/log-aggregation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [loki](<https://devfeed.tech/tags/loki.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud Logs full-text search adds a secondary index to Loki so supported searches for rare strings can skip data that cannot contain a match, reducing scans across long time ranges. It accelerates exact string filters (`|=`), literal regex searches (`|~`, including `(?i)`), and certain filters on structured metadata, labels, or parsed attributes; some advanced regex constructions are unsupported. The article reports about 10% additional compute and storage costs at Grafana Cloud scale, partly offset by reduced query compute. It preserves Loki's schemaless model, existing ingestion pipelines, labels, and LogQL. The feature is generally available in Grafana Cloud Logs at no additional cost. To try it, open Explore, select the Logs data source, add a stream selector and line filter, choose a longer time range, and run the query. A DATEV eG example reports reducing searched data from nearly 1 TB to around 100 GB and query time from three minutes to under three seconds for newly submitted logs.

### Source excerpt

A support ticket comes in with one clue: a transaction ID. The answer is somewhere in your logs, but you don't know which service logged it, which pod handled it, or which day it happened. So you write the query you always write, {service="payments"} |= "txn-123456", widen the time range to the last two weeks, and wait. Then the query times out. Loki was originally built around a simple idea: index labels, not log content, and store compressed logs cheaply in object storage. That design keeps storage costs low and operations light, and it's why teams keep choosing Loki and Grafana Cloud Logs, the fully managed log aggregation system powered by Loki, as their log volumes grow. For most queries, this model works very well. But when you search for a highly unique value, like a request ID, job ID, user ID, or device ID, labels can only narrow the search so far. Loki still has to read a lot of raw log data to find a handful of matching lines. At terabyte and petabyte scale, that process can be slow and costly. To fix that, we built full-text search for Grafana Cloud Logs, a capability based on the Logline technology Grafana Labs acquired in April 2026. Full-text search, now generally available in Grafana Cloud Logs, adds a purpose-built secondary index to Loki, so you can find specific log lines across weeks of logs in seconds without a full scan. You go straight to the one transaction ID, user ID, or error that matters and cut time to resolution. "When I ran our first query on newly submitted logs after enabling Logline, the improvement was clear," said Timo Kirzdörfer, OpenTelemetry & Grafana Cloud Admin, DATEV eG. "We went from processing nearly a terabyte of logs in three minutes to around 100 gigabytes in under three seconds. That represents an 80-90% reduction in the volume of logs searched for newly submitted logs, and we saw the results immediately." In this post, we'll explore how full-text search speeds up log investigations. You can also learn more in the Obse

## What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more

DevFeed: [What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more](<https://devfeed.tech/articles/what-s-new-in-pyroscope-profile-more-of-your-workflows-troubleshoot-with-ai-agents-and-more-133569.md>)

Original publisher: [Read original article](<https://grafana.com/blog/whats-new-in-pyroscope-profile-more-of-your-workflows-troubleshoot-with-ai-agents-and-more/>)

Author: Tiffany Jernigan

Published: 2026-11-13T17:14:29Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Python](<https://devfeed.tech/topics/python.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-profiling](<https://devfeed.tech/tags/continuous-profiling.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-pyroscope](<https://devfeed.tech/tags/grafana-pyroscope.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [net](<https://devfeed.tech/tags/net.md>), [observability](<https://devfeed.tech/tags/observability.md>), [profile](<https://devfeed.tech/tags/profile.md>), [traces](<https://devfeed.tech/tags/traces.md>), [troubleshoot](<https://devfeed.tech/tags/troubleshoot.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Pyroscope adds memory profiling for Python and Rust, .NET profiling on Windows, and ways to inspect individual profiles and call paths. Python's SDK reports heavy allocations and memory still in use; Rust uses jemalloc to report live memory. Windows support is x64 and begins with profiler 1.3.0; .NET 8-10 offer the same profile types as Linux, while .NET Framework 4.7 and later support CPU and wall-time profiling. Windows support is in public preview. The gcx CLI can query Pyroscope profiles, rank services by resource use, list costly individual profiles (exemplars), inspect a selected profile, and export pprof files. Grafana also displays exemplars and adds an expandable Call Tree to trace paths to expensive functions. Exemplars require Pyroscope 2.0's v2 storage layer; Call Tree is available in Profiles Drilldown 2.3.0 and later, Explore, and the flame graph panel in Grafana 13.3, with a feature toggle required on earlier Grafana versions.

### Source excerpt

When an application slows down or memory usage keeps climbing, knowing which code is responsible can help you find a fix faster. Continuous profiling gives you that visibility, so you can see where your application spends resources such as CPU time and memory. We've made updates to Pyroscope, our open source continuous profiling database, that make it easier to profile your applications, find performance bottlenecks, and optimize your code, whether you're doing the work yourself or with an AI agent. Highlights include: Profile more of your workloads: Memory profiling for Python and Rust, and .NET support on Windows, helps you find performance bottlenecks across more of your services. Let AI agents work with your profiling data: Pyroscope commands in gcx, the Grafana CLI, let an agent query your profiles directly. See more of your profiling data in Grafana: Exemplars and a new Call Tree view help you explore your profiles visually, whether you're investigating on your own or looking at what an agent found. Many of these capabilities build directly on Pyroscope 2.0, the ground-up rearchitecture of Pyroscope that makes continuous profiling more cost-effective at scale (in our production environment, it reduced the symbol storage footprint by up to 95%). For example, exemplars require the v2 storage layer that Pyroscope 2.0 is built on. Read on to learn more about some of the latest updates. And for a full list of recent changes, see the release notes for Pyroscope and Profiles Drilldown. Profile more of your workloads Memory profiling and Windows support have been some of the most frequently requested features for Pyroscope. If you run Python or Rust services, you can now use the Pyroscope SDKs to see where their memory goes, not just their CPU time. If you run .NET applications on Windows, you can now profile those, too. Find memory leaks and heavy allocation: memory profiling for Python Memory issues can be hard to track down from metrics alone. A container's memory

## An early look at the Grafana UI refresh: Building a clearer, more consistent user experience

DevFeed: [An early look at the Grafana UI refresh: Building a clearer, more consistent user experience](<https://devfeed.tech/articles/an-early-look-at-the-grafana-ui-refresh-building-a-clearer-more-consistent-user-experience-131223.md>)

Original publisher: [Read original article](<https://grafana.com/blog/an-early-look-at-the-grafana-ui-refresh-building-a-clearer-more-consistent-user-experience/>)

Author: Kirby Peterman

Published: 2026-11-12T17:01:40Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [preview](<https://devfeed.tech/tags/preview.md>), [product-design](<https://devfeed.tech/tags/product-design.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [traces](<https://devfeed.tech/tags/traces.md>), [ui](<https://devfeed.tech/tags/ui.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

Grafana 13.3 introduced the first phase of a visual refresh aimed at reducing design inconsistency and making information hierarchy clearer across workflows. It adds new default light and dark themes with accessibility compliance improved by design, reduces the number of component types and variants, and updates fonts, borders, shadows, cards, panels, and drawers. This is a gradual visual change: navigation remains the same and plugins have no breaking changes. The refreshed UI is in public preview on Grafana Cloud and self-managed Grafana; self-managed users can enable it with the `grafana.visualDesignRefresh` feature toggle and switch back to the previous styling at any time. Grafana Labs is collecting feedback through community Slack and a temporary in-app survey to guide future iterations.

### Source excerpt

Whether you're investigating an incident or just exploring your data, a clear, consistent UI helps you move between workflows and find what matters faster. As Grafana has grown to support more use cases, we've seen opportunities to improve on that experience. That's why, as part of the Grafana 13.3 release, we introduced the first phase of our biggest visual refresh since Grafana 7. We're approaching this work in phases, with the refreshed UI currently in public preview in both Grafana Cloud and self-managed versions of Grafana, and your feedback will play a major role in shaping what comes next. In this post, we'll give you a closer look at why we decided to make this change now, why we think visual aesthetics matter in a UI, and the impact this will have on the Grafana user experience. You can also check out some of the visual updates in the video below. Starting with why "Purposes are deduced from behavior, not from rhetoric or stated goals." - Donella Meadows At Grafana Labs, our culture empowers individuals and teams to identify user needs, build solutions quickly, ship iteratively, and work in the open. This has allowed us to cover a large range of use cases with Grafana. But moving fast can come with challenges, including design debt, which leads to inconsistent and sometimes conflicting visual cues, workflows, and GUIs. We were aware of these challenges, but our focus remained steadfast on providing new functionality and supporting as many use cases as possible. Meanwhile, over the last year, the product design team has worked with our engineers to build new interaction patterns to support AI solutions like Grafana Assistant and Assistant Workspace. Building these patterns opened the door to curiosity, and we started experimenting with new visual forms, colors, shapes, and effects that laid the groundwork for the refresh. Through this work, our approach to UI style and aesthetics evolved, and so did our purpose: alongside supporting new workflows and use cas

## Run cost-effective, always-on agents to monitor your environment: the engineering behind Watchers

DevFeed: [Run cost-effective, always-on agents to monitor your environment: the engineering behind Watchers](<https://devfeed.tech/articles/run-cost-effective-always-on-agents-to-monitor-your-environment-the-engineering-behind-watchers-124791.md>)

Original publisher: [Read original article](<https://grafana.com/blog/run-cost-effective-always-on-agents-to-monitor-your-environment-the-engineering-behind-watchers/>)

Author: William Dumont

Published: 2026-11-09T16:30:31Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-investigation](<https://devfeed.tech/tags/agentic-investigation.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [attention](<https://devfeed.tech/tags/attention.md>), [cause](<https://devfeed.tech/tags/cause.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [control](<https://devfeed.tech/tags/control.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [environment](<https://devfeed.tech/tags/environment.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Watchers aim to catch issues that fixed alert rules miss while keeping continuous monitoring costs low. During one-time calibration, a background agent maps telemetry, uses existing alerts and dashboards, samples signals across the prior week, validates checks, and saves a compact decision guide. Each run then uses code to fetch and compare metrics, track Loki log patterns, and report deploys; one small, fast model reviews the resulting digest and decides whether to notify or launch an investigation. Internal Watchers reportedly cost a median of under $5 monthly, with 41 of 43 under $10; cost depends on run frequency and monitored scope, while calibration and launched investigations add costs. The team says its watcher found more than 10 customer-affecting production bugs, though it can misidentify causes. Watchers support listed Grafana telemetry sources, HTTP APIs via Infinity, and destinations including Slack, Teams, webhooks, and Grafana Alerting. They complement alert rules rather than replace them.

### Source excerpt

Alert rules are great for the failures you can predict, but they fall short on the ones you can't. With the advent of modern AI, you might think the solution is to swarm your stack with agents that monitor every last detail, but that can quickly lead to astronomical bills. And those are the gaps Watchers fill: catching what alerts miss while keeping costs in control. Generally Available as of ObservabilityCON 2026, Watchers are always-on agents in Grafana Assistant. You describe what to monitor (in natural language) and pick your data sources, and the watcher learns what "normal" looks like and tells you when you drift from that state. Ultimately, this helps you surface problems without needing an alert, giving you wider coverage and more confidence in your system. But how do we keep Watchers cost-effective for our customers, especially in comparison to building your own agent that runn around the clock? For example, let's say you deploy your own version of a watcher that checks in every 10 minutes, which means it runs 4,320 times a month. If each run were an agentic investigation, which cost us between $0.56 and $1.26 in a recent experiment, that one watcher you built would cost thousands of dollars a month. Yet the Watchers running on our own Grafana Cloud stack cost a median of less than $5 a month. In this post, I'll show you the engineering behind that number, which mostly comes down to one question: where do you actually need an LLM's intelligence, and how much of it? The TL;DR on Watchers Watchers keeps an eye on one things you care about, such as a service, a dependency, or a fix you shipped after an incident. Think of it as the dashboard check you'd otherwise do by hand, done around the clock. It stays quiet until something needs attention, then it sends you its assessment and the evidence behind it. For critical findings, it can also launch an Investigation in Assistant to find the cause. Here's the gist of how it helps you identify potential issues in a c

## Any agent anywhere: How to use Grafana Cloud with Claude, Cursor, and any other AI agent

DevFeed: [Any agent anywhere: How to use Grafana Cloud with Claude, Cursor, and any other AI agent](<https://devfeed.tech/articles/any-agent-anywhere-how-to-use-grafana-cloud-with-claude-cursor-and-any-other-ai-agent-121824.md>)

Original publisher: [Read original article](<https://grafana.com/blog/any-agent-anywhere-how-to-use-grafana-cloud-with-claude-cursor-and-any-other-ai-agent/>)

Author: Gianni Baiardi

Published: 2026-11-06T18:37:07Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [mcp grafana](<https://devfeed.tech/topics/mcp-grafana.md>), [cursor](<https://devfeed.tech/topics/cursor.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-observability](<https://devfeed.tech/tags/agentic-observability.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-data](<https://devfeed.tech/tags/cloud-data.md>), [cloud-observability](<https://devfeed.tech/tags/cloud-observability.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud can provide observability context to AI agents through three routes: Grafana Assistant within Grafana Cloud, the Grafana Cloud MCP server for compatible clients such as Claude, ChatGPT, and Codex, and the gcx command-line tool for coding agents and scripts. The MCP server lets agents query alerts, dashboards, and telemetry; MCP Apps can show interactive Grafana views in clients that support them. For coding work, a dashboard can pass a panel's query, filters, and time range to an agent such as Cursor, which can use gcx and its curated agent skills to explore services, databases, and frontend sessions. Shell-capable coding agents can use gcx. The excerpt also describes Hermes using both MCP and gcx from Slack to investigate transfer issues and report findings with Grafana links. Available client features vary: interactive views require MCP Apps support. The excerpt does not include the article's promised setup steps.

### Source excerpt

AI agents are becoming part of everyday engineering workflows, helping teams write code, troubleshoot issues, and automate tasks. But to be truly useful in production, these agents need access to more than code. They also need observability data and context to understand what's happening across your systems, investigate problems, and help you take action. At Grafana Labs, we believe that context should be available wherever you work. That's one of the core ideas behind Grafana Cloud as the open agentic observability platform: the flexibility to work with your observability data through the AI agents you prefer--whether it's Grafana Assistant, a coding agent in your IDE, or a tool you've built yourself--so you can investigate and troubleshoot issues without switching tools. In this post, we'll explore how to bring Grafana Cloud into your agentic workflows using tools like the Grafana Cloud MCP server and gcx, with practical examples along the way. You can also check out our ObservabilityCON 2026 talk in the video below to learn more. Three ways to use Grafana Cloud with AI agents There are multiple ways to bring Grafana Cloud observability data and context into your AI workflows, depending on where and how you prefer to work: Work directly in Grafana Cloud: Use Grafana Assistant, the AI-powered assistant built into Grafana Cloud, to investigate issues and interact with your observability data. Connect your preferred AI agent: Use the Grafana Cloud MCP server to bring Grafana Cloud data into compatible tools such as Claude, ChatGPT, and Codex. Work with coding agents and scripts: Use gcx, the Grafana Cloud command-line tool, to give coding agents access to observability data directly from their working environment. Whether you're working directly in Grafana Cloud with Grafana Assistant or using your own AI agents, you can choose the approach that works best for you. Let's look at how the Grafana Cloud MCP server and gcx make that possible outside of Grafana Cloud. Inves

## What's new with Grafana variables: less clutter, easier reuse across dashboards, and more

DevFeed: [What's new with Grafana variables: less clutter, easier reuse across dashboards, and more](<https://devfeed.tech/articles/what-s-new-with-grafana-variables-less-clutter-easier-reuse-across-dashboards-and-more-119821.md>)

Original publisher: [Read original article](<https://grafana.com/blog/whats-new-with-grafana-variables-less-clutter-easier-reuse-across-dashboards-and-more/>)

Author: Haris Rozajac

Published: 2026-11-05T19:25:32Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [api-platform](<https://devfeed.tech/tags/api-platform.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [database](<https://devfeed.tech/tags/database.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [query](<https://devfeed.tech/tags/query.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [template](<https://devfeed.tech/tags/template.md>), [traces](<https://devfeed.tech/tags/traces.md>), [variable](<https://devfeed.tech/tags/variable.md>), [variables](<https://devfeed.tech/tags/variables.md>)

### AI overview

Grafana adds section-level variables (generally available) and cross-dashboard variables (public preview) to reduce dashboard clutter and repeated maintenance. Variables scoped to a row or tab apply only to its panels; Grafana resolves them from the nearest section outward to parent sections and then the dashboard. Sections can also have their own Filter and Group by controls, and variables move up a level if a section is ungrouped. Cross-dashboard variables can be global or folder-scoped. Their definition is shared, while each dashboard retains its own selected value; dashboards must opt in to specific variables or all variables in a scope. Local dashboard variables override global ones, and section variables can override both. Cross-dashboard definitions are managed under Dashboards > Variables and are read-only in dashboard edit mode. In public preview, they are separate v2beta1 Variable API resources, manageable through Grafana's API or Terraform's grafana_apps_generic_resource; dashboards can also opt in through configuration.

### Source excerpt

Template variables are one of the most used features in Grafana, providing users with a dropdown to turn one dashboard into hundreds: pick a different cluster, region, or service, and every panel updates. For most of Grafana's history, variables had a single home at the top of the dashboard. Each dashboard had one flat list of variables, and that list was shared by every panel on it. But as dashboards grew in size and number, those controls became harder to organize and maintain. The top of a dashboard could get crowded with dropdowns that only applied to certain panels, while shared controls were copied across dashboards and had to be updated individually. To address these challenges, we've rolled out two new features in Grafana: Section-level variables for rows and tabs (generally available): these variables let you place controls near the panels they affect, reducing clutter at the top of the dashboard. Cross-dashboard variables (public preview): these are variables you can define once and reuse across dashboards, keeping configurations consistent and easier to maintain. In this post, we'll take a closer look at each variable type, its use cases, and how to get started. Section-level variables: define and manage variables by row or tab Section-level variables let you define variables and filters for a specific row or tab, so they apply only to the panels inside that section. Placing a control next to the panels it affects makes it clear what a selection will change, and it keeps the top of the dashboard uncluttered. Let's say you want two $instance dropdowns, one for your API gateway panels and one for your database panels. Traditionally, with one flat namespace, you'd end up with names like $api_instance and $db_instance, or you'd split the dashboard into two. Now, with section-level variables, the API gateway section and the database section can each have its own $instance variable with its own query and selected value. Both sections still share the dashboard t

## Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview

DevFeed: [Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview](<https://devfeed.tech/articles/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview-116280.md>)

Original publisher: [Read original article](<https://grafana.com/blog/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview/>)

Author: Bejal Lewis

Published: 2026-11-03T21:32:18Z

Content type: news

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collector](<https://devfeed.tech/tags/collector.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [engine](<https://devfeed.tech/tags/engine.md>), [engines](<https://devfeed.tech/tags/engines.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fleet-management](<https://devfeed.tech/tags/fleet-management.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [installation](<https://devfeed.tech/tags/installation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [loki](<https://devfeed.tech/tags/loki.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Alloy's OTel engine reached Public Preview in Alloy v1.21.0, offering native OpenTelemetry Collector pipelines alongside Alloy's cross-ecosystem default engine. It runs standard collector YAML without translation; existing `otelcol` workflows can use `alloy otel`, and deployments are supported through the upstream Helm chart, OpenTelemetry Operator v0.153.0+, or Alloy packages in OTel mode. Fleet Management can centrally apply configuration through the experimental `otel-supervisor` command. The engines cannot pass data directly; the experimental `alloyengine` extension runs Alloy configuration inside the collector as a bridge, but the article says it is unsupported for production. Examples include Database Observability and cloud provider exporters; native collector components are still in progress. Planned OTel work includes support bundles, while default-engine work targets more reliable Prometheus remote write and Loki delivery.

### Source excerpt

Many Grafana Cloud customers love what Alloy offers them, but we're also seeing a growing base of users who feel the same way about the OpenTelemetry Collector. We want to make it easy for customers to make the decision that makes the most sense, regardless of their preference. When we introduced the OpenTelemetry engine for Grafana Alloy, we set out to give teams a way to run native OTLP pipelines without giving up the power and flexibility Alloy is known for. Since then we've kept building: ironing out service installation support, enabling Fleet Management, and folding in feedback from early users. Today, as of Alloy v1.21.0, we're happy to share that the OTel engine has moved into Public Preview, running right alongside the default engine you already know. In this post, we'll dig into when you'd reach for each engine, walk through some of the most interesting use cases we've seen so far, and give a preview of where both engines are headed next. The motivation behind each engine Before diving into specific new features, let's recap why we have two engines in Alloy. Default engine The default engine is a cross-ecosystem engine at its core; it's not tied to any single wire format or vendor. It can just as easily run a Prometheus pipeline, an OTLP pipeline, or a Loki pipeline, all defined using Alloy's own configuration syntax. That flexibility is what makes it a Swiss army knife: the same engine that scrapes Prometheus metrics can pull in logs over syslog for logs, ingest OTLP, scrape Prometheus metrics from embedded exporters, and route all of it to wherever it needs to go. OpenTelemetry engine There's a lot to like about being able to speak every ecosystem's language. But the telemetry landscape itself is moving in the opposite direction. Rather than translating between formats, the industry is increasingly converging on a single, shared model defined by the OpenTelemetry specification. That's what an OpenTelemetry Collector actually is: a pipeline that treats OT

## Trace linkage: connect the dots between your app traces and database queries

DevFeed: [Trace linkage: connect the dots between your app traces and database queries](<https://devfeed.tech/articles/trace-linkage-connect-the-dots-between-your-app-traces-and-database-queries-116281.md>)

Original publisher: [Read original article](<https://grafana.com/blog/trace-linkage-connect-the-dots-between-your-app-traces-and-database-queries/>)

Author: Shirley

Published: 2026-11-03T15:05:03Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [database](<https://devfeed.tech/tags/database.md>), [database-observability](<https://devfeed.tech/tags/database-observability.md>), [execution](<https://devfeed.tech/tags/execution.md>), [explain](<https://devfeed.tech/tags/explain.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [history](<https://devfeed.tech/tags/history.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [performance](<https://devfeed.tech/tags/performance.md>), [plan](<https://devfeed.tech/tags/plan.md>), [queries](<https://devfeed.tech/tags/queries.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [tempo](<https://devfeed.tech/tags/tempo.md>), [text](<https://devfeed.tech/tags/text.md>), [trace](<https://devfeed.tech/tags/trace.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

### AI overview

Grafana Cloud Database Observability's trace linkage connects OpenTelemetry database spans to query context collected by Alloy. It uses query text, database system, and database name; spans with `db.query.text` or legacy `db.statement` may match without further application instrumentation. For more precise execution-level matches, optional sqlcommenter propagation places trace and span IDs in SQL comments, which Alloy extracts from query sample logs. Exact matches are best-effort: Alloy may miss short-lived executions or fail to poll them, sqlcommenter does not support every database engine and may affect database caches. When exact matching is unavailable, trace linkage accounts for differences in query formatting, comments, literals, and parameter placeholders to find matching query text, allowing users to inspect samples, historical performance, schema, and explain plans. Setup requires an OpenTelemetry-instrumented application sending traces to Grafana Cloud and Database Observability configured.

### Source excerpt

When an application request slows down, a trace can show a database call. Finding the database query behind it can be tedious, requiring you to switch between traces and database telemetry, as well as match timestamps or query text by hand. In Grafana Cloud, the Database Observability app already provides a window into all of your database telemetry, including query samples, performance history, and explain plan. But what if you could jump from that database call in the trace straight to its query details? OpenTelemetry database semantic conventions stabilized last year, giving us all a dependable shared language for describing database operations. That foundation has opened the door for what we call trace linkage, now Generally Available in Database Observability! What is trace linkage? With trace linkage, we try to provide a connection between OpenTelemetry-instrumented applications and database telemetry collected with Alloy. In other words, when you give us these previously-disjoint puzzle pieces, we'll do our best to provide you as much supporting information between these two elements as we can. And we'll do it without making you tediously piece together timestamps and logs. From a database span in a trace, you'll see a link on the query text. Clicking from there, the app searches for a connection between your database query and our opinionated view of your most relevant data in the Database Observability app. You can explore sampled query execution data or check out the query's historical performance, alongside that query's related schema and explain plan. This connection builds on the database attributes your OpenTelemetry instrumentation already emits. Grafana Cloud Traces, powered by Tempo, retain those attributes, and trace linkage uses the query text, database system, and database name to connect a database span to its supporting query context in Database Observability. We support the stable conventions like db.query.text and its legacy equivalent db.sta

## Instrumentation Hub in Grafana Cloud: start easier, stay in control

DevFeed: [Instrumentation Hub in Grafana Cloud: start easier, stay in control](<https://devfeed.tech/articles/instrumentation-hub-in-grafana-cloud-start-easier-stay-in-control-113326.md>)

Original publisher: [Read original article](<https://grafana.com/blog/instrumentation-hub-start-your-observability-journey-easier-and-still-stay-in-control/>)

Author: Fabian Stäber

Published: 2026-11-02T15:44:53Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [helm](<https://devfeed.tech/tags/helm.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [opentelemetry-sdk](<https://devfeed.tech/tags/opentelemetry-sdk.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud's Instrumentation Hub is generally available for Kubernetes clusters running Linux. Install Alloy with a Helm command; it discovers workloads and shows what is instrumented. Teams can use the Grafana Cloud UI, API automation, or an LLM agent to select what telemetry to collect, then adjust scope and signals by namespace to manage coverage and spend. The Hub supports eBPF instrumentation and selective OpenTelemetry SDK injection, which the excerpt says adds runtime insight and can enrich baseline service visibility without extra collection layers or disruptive restarts. It also describes one-click Kubernetes Monitoring and populating Grafana Cloud's Knowledge Graph. The excerpt does not specify supported languages or deployment requirements beyond Linux Kubernetes.

### Source excerpt

It's no secret that getting started with observability can be much harder than it should be. That's why, at ObservabilityCon 2025, we introduced Instrumentation Hub: a guided, scalable way to roll out observability coverage while still keeping you in control. Today, we're excited to announce that Instrumentation Hub is now Generally Available in Grafana Cloud. As we hinted at before, this new iteration introduces selective OpenTelemetry SDK injection, giving you deeper runtime insights for a wide range of languages to complement eBPF instrumentation with a single click. What is the Instrumentation Hub? Instrumentation Hub makes the biggest bottleneck of starting with observability, instrumentation, faster and easier by leveraging open source eBPF and OTel injection. At Grafana Labs, we're champions of open-standards-based observability, but we also realize that getting meaningful coverage of your systems can often mean months of manual toil. Each layer requires its own instrumentation approach, balancing technology tradeoffs, and unique brittle steps. Organizational challenges exacerbate this process, making observability a moving target with uneven coverage, persistent blind spots, and ultimately leaving you wondering if the effort was worth the pain. We believe there's a better way. Instrumentation Hub is a control plane for remote discovery and selective auto-instrumentation. It helps you go from zero to meaningful telemetry in a matter of minutes by removing the bottleneck of having to apply instrumentation by hand. How Instrumentation Hub works The premise is simple: you run a single Helm command on your Kubernetes cluster to install Alloy, our distribution of the OpenTelemetry Collector. Once installed, Instrumentation Hub automatically catalogs everything that's running on the cluster, structured by namespace and technology. Teams can immediately see what exists, what's instrumented, and what isn't. Then, you use either the Grafana Cloud UI, an API automation

## Grafana 13.3 release: manage variables across dashboards, share findings with Notebooks, a UI refresh, and more

DevFeed: [Grafana 13.3 release: manage variables across dashboards, share findings with Notebooks, a UI refresh, and more](<https://devfeed.tech/articles/grafana-13-3-release-manage-variables-across-dashboards-share-findings-with-notebooks-a-ui-refresh-and-more-107143.md>)

Original publisher: [Read original article](<https://grafana.com/blog/grafana-13-3-release-all-the-latest-features/>)

Author: Grafana Labs Team

Published: 2026-10-29T15:01:42Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [capture](<https://devfeed.tech/tags/capture.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration-drift](<https://devfeed.tech/tags/configuration-drift.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [control](<https://devfeed.tech/tags/control.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [define](<https://devfeed.tech/tags/define.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [environment](<https://devfeed.tech/tags/environment.md>), [explore](<https://devfeed.tech/tags/explore.md>), [feature](<https://devfeed.tech/tags/feature.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [manage](<https://devfeed.tech/tags/manage.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [release](<https://devfeed.tech/tags/release.md>), [share](<https://devfeed.tech/tags/share.md>), [traces](<https://devfeed.tech/tags/traces.md>), [ui](<https://devfeed.tech/tags/ui.md>), [variables](<https://devfeed.tech/tags/variables.md>)

### AI overview

Grafana 13.3 adds centrally managed cross-dashboard variables, editable Notebooks for gathering panels, queries, Assistant findings, and notes, plus the first phase of a visual refresh. Variables can be scoped globally or to a folder; viewers can change their values, while configuration remains centrally managed. These features are in public preview, and self-managed users must enable their respective feature toggles. Notebooks are gradually rolling out to Grafana Cloud. The visual refresh updates themes, components, and typography while keeping workflows and navigation the same; plugins using standard Grafana components and theme tokens inherit the changes, while custom-styled plugins can migrate on their own timeline. Grafana Assistant can now propose a dashboard plan for review and preview before building, and users can undo an Assistant turn, including changes to multiple panels. Dashboard plans are in public preview; undo is generally available.

### Source excerpt

Grafana 13.3 is here, bringing more consistency and control to how you work across Grafana. Cross-dashboard variables help you manage shared dashboard controls from one place, while Notebooks let you capture and share findings from across Grafana in a single, editable document. You'll also get a first look at Grafana's biggest visual refresh since Grafana 7, along with new ways to guide and refine dashboards built with Grafana Assistant. Below are just some of the highlights from this release. You can explore all of the updates in the changelog or our What's new in Grafana 13.3 documentation. Define a variable once and use it across dashboards Available in public preview in all editions of Grafana When multiple dashboards use the same variable, such as an environment, region, or cluster selector, managing it separately in each dashboard creates duplicate work and can lead to configuration drift. To address this, we're rolling out cross-dashboard variables, which let you define a variable once and reuse it across dashboards in your Grafana organization. You can create and manage these variables from Dashboards > Variables, and scope each one as either: Global: available to every dashboard in the organization Folder: available only to dashboards in the same folder When you edit a dashboard, add a variable from the sidebar and select Global or folder variable. Grafana shows only the variables available to that dashboard's scope, and you can add them one at a time or all at once. Viewers can still change the variable's value on the dashboard, while its configuration stays managed centrally, so shared controls stay consistent without editing every dashboard that uses them. To try cross-dashboard variables in self-managed Grafana, enable the grafana.dashboardGlobalVariables feature toggle. To learn more, refer to the cross-dashboard variables documentation. Consolidate and share your findings with Notebooks Available in public preview in all editions of Grafana An investi

## Evaluate AI models for observability: o11y-bench joins Fireworks' Specialized Intelligence Index and reaches v1.1

DevFeed: [Evaluate AI models for observability: o11y-bench joins Fireworks' Specialized Intelligence Index and reaches v1.1](<https://devfeed.tech/articles/evaluate-ai-models-for-observability-o11y-bench-joins-fireworks-specialized-intelligence-index-and-reaches-v1-1-105724.md>)

Original publisher: [Read original article](<https://grafana.com/blog/evaluate-ai-models-for-observability-o11y-bench-joins-fireworks-specialized-intelligence-index-and-reaches-v1-1/>)

Author: Sean Porter

Published: 2026-10-28T16:08:24Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Ground truth / benchmark quality](<https://devfeed.tech/topics/ground-truth-benchmark-quality.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [litellm](<https://devfeed.tech/topics/litellm.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-training](<https://devfeed.tech/tags/ai-training.md>), [ai-training-and-inference](<https://devfeed.tech/tags/ai-training-and-inference.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bench](<https://devfeed.tech/tags/bench.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-labs](<https://devfeed.tech/tags/grafana-labs.md>), [index](<https://devfeed.tech/tags/index.md>), [inference](<https://devfeed.tech/tags/inference.md>), [integration](<https://devfeed.tech/tags/integration.md>), [intelligence](<https://devfeed.tech/tags/intelligence.md>), [litellm](<https://devfeed.tech/tags/litellm.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [models](<https://devfeed.tech/tags/models.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

o11y-bench evaluates whether AI agents can complete observability and SRE tasks using evidence from a running Grafana stack, rather than merely produce plausible answers. Agents use the Grafana MCP server on synthetic telemetry across 64 tasks in six areas; each task runs three times, with Pass³ measuring average performance and Pass@3 recording whether the agent succeeds at least once. Version 1.1 checks claims against environment facts, verifies cited traces in Tempo, grades dashboard changes through saved-state diffs, and treats failed ground-truth queries as grading errors. Saved facts allow regrading without rerunning agents. A no-tools control failed all 64 tasks. The benchmark is open source and now supports Fireworks inference for serverless and account-deployed models through its LiteLLM-backed agent. Version 1.1 results establish a new baseline and are not directly comparable with 1.0.

### Source excerpt

When evaluating AI models for observability, generating a plausible query or explanation isn't enough. Teams need to know whether an agent's conclusions are supported by telemetry, whether its changes to dashboards actually work, and whether it can deliver reliable results consistently. This is why we built o11y-bench, Grafana Labs' open benchmark for evaluating AI models on observability and SRE tasks. And today, we're excited to share two updates: o11y-bench is now part of the Specialized Intelligence Index from Fireworks, the AI training and inference platform, and we're releasing o11y-bench 1.1, with updates that make grading more grounded, consistent, and reproducible. Bringing o11y-bench to the Specialized Intelligence Index The Specialized Intelligence Index brings together practitioner-built benchmarks for comparing how open, closed, and specialized AI models perform on domain-specific work, from healthcare and finance to cybersecurity and software engineering. It helps teams identify the best models for their workloads, understand where specialization adds value, and evaluate tradeoffs between quality, cost, and speed. With o11y-bench now part of the index, SRE, platform engineering, and observability teams can explore how AI models perform on real observability workflows--from querying metrics, logs, and traces to investigating incidents and managing Grafana dashboards--alongside benchmarks for other specialized domains and use cases. Run the benchmark with Fireworks inference o11y-bench also now supports Fireworks as an inference provider in its default LiteLLM-backed agent. This means teams can evaluate both serverless models and models deployed within their own Fireworks accounts, using the same reproducible workflow available for other providers. The integration handles Fireworks credentials, deployment names, and reasoning settings so benchmark runs are configured consistently. This makes it easier to reproduce results from the index or evaluate Firewor

## Agent Observability FAQ: Understand the value of monitoring, evaluating, and improving your AI agents

DevFeed: [Agent Observability FAQ: Understand the value of monitoring, evaluating, and improving your AI agents](<https://devfeed.tech/articles/agent-observability-faq-understand-the-value-of-monitoring-evaluating-and-improving-your-ai-agents-102850.md>)

Original publisher: [Read original article](<https://grafana.com/blog/agent-observability-faq-understand-the-value-of-monitoring-evaluating-and-improving-your-ai-agents/>)

Author: Aishlee Kailey

Published: 2026-10-27T14:32:18Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [data loss prevention](<https://devfeed.tech/topics/data-loss-prevention.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [change](<https://devfeed.tech/tags/change.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [compare](<https://devfeed.tech/tags/compare.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data](<https://devfeed.tech/tags/data.md>), [debug](<https://devfeed.tech/tags/debug.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [faq](<https://devfeed.tech/tags/faq.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud's Agent Observability combines monitoring, evaluations, experiments, and safeguards to help teams diagnose and improve agents. It tracks latency, errors, tokens, and cost, and can trace conversations and multi-agent handoffs; prompt changes are versioned for comparisons, while experiments can serve as CI deployment gates. Evaluations can combine deterministic checks with LLM judges. Guards can detect or redact PII and block risky tool calls. OpenTelemetry spans are supported without its SDK, and metrics are available in Prometheus for custom dashboards and alerts. The service captures prompts, responses, tool calls, and usage; SDK redaction and role-based access help limit exposure, while coding agents send metadata unless full content is enabled. Coding-agent sessions can also stay local in a free open-source app. Pricing uses separate meters for generations, evaluation/guard tokens, and standard metrics and traces; Free and Pro include monthly allowances of 30,000 generations and 25 million evaluation/guard tokens.

### Source excerpt

Agents have quickly become part of the tech landscape as organizations embrace AI across their businesses. But embracing agents also means embracing the monitoring best practices that have long been part of engineers' workflows: tracking performance, catching errors, and responding to incidents But it doesn't stop there. Agents also introduce new challenges. They can give different answers to the same question, be confidently wrong without throwing an error, and turn one request into a long chain of model and tool calls that's hard to debug. A small prompt change can shift behavior as much as a code deploy. And because agents act on what they read, they open the door to new risks like prompt injection and leaked sensitive data. It's a lot to learn, but that's why we built Agent Observability, now generally available, as part of our growing set of AI-enabled features in Grafana Cloud. It improves your agents by helping your teams: Monitor performance and cost: Track latency, errors, token usage, and costs, and drill into individual conversations when something goes wrong. Evaluate agent quality: Use built-in or custom evaluators to measure quality and detect issues like PII or prompt injection. Test changes before you ship: Compare models, prompts, and other changes with offline experiments to catch regressions. Build evaluations into CI/CD: Use experiments as deployment gates and track agent versions as you iterate. Agent Observability was born out of our own challenges managing agents at scale, and it's the same tool we use internally today. In this blog, I'll address some of the common questions we get from customers. Everything you want to know about Agent ObservabilityMonitoring, evaluating, and improving agents Q: Why use Agent Observability to monitor my agents? Agents are production workloads, and they need the same visibility as the services they touch. Agent Observability runs in Grafana Cloud alongside your metrics, logs, traces, and profiles, so you can t

## Spend less time on operational busywork and resolve incidents faster with Grafana Workflows

DevFeed: [Spend less time on operational busywork and resolve incidents faster with Grafana Workflows](<https://devfeed.tech/articles/spend-less-time-on-operational-busywork-and-resolve-incidents-faster-with-grafana-workflows-92997.md>)

Original publisher: [Read original article](<https://grafana.com/blog/spend-less-time-on-operational-busywork-and-resolve-incidents-faster-with-grafana-workflows/>)

Author: Michael Wettick

Published: 2026-10-21T15:06:02Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [approach](<https://devfeed.tech/tags/approach.md>), [attention](<https://devfeed.tech/tags/attention.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [away](<https://devfeed.tech/tags/away.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [blueprints](<https://devfeed.tech/tags/blueprints.md>), [but](<https://devfeed.tech/tags/but.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [faster](<https://devfeed.tech/tags/faster.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-cloud-irm](<https://devfeed.tech/tags/grafana-cloud-irm.md>), [less](<https://devfeed.tech/tags/less.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operational](<https://devfeed.tech/tags/operational.md>), [time](<https://devfeed.tech/tags/time.md>), [traces](<https://devfeed.tech/tags/traces.md>), [with](<https://devfeed.tech/tags/with.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Grafana Workflows, in public preview, automates repeatable incident and operations steps across Grafana Cloud and other tools, with optional Grafana Assistant steps to interpret supplied context. The major incident kickoff blueprint can create a linked Slack channel, assign an on-call commander from the configured schedule, post response instructions, bookmark the runbook and incident record, and note when no commander is on call. Teams can add support paging and Slack updates; Assistant can prepare evidence-linked incident briefings or draft customer-facing updates for support review. Other blueprints prepare handoff reports from recent incidents and alert groups or weekly service health summaries from SLO, error-budget, error, latency, incident, and alert data. Workflows can also assess customer impact against a configured threshold to trigger escalation. Users can adapt blueprints or ask Assistant to build a workflow; new workflows open disabled for review and testing, and run history exposes step inputs, outputs, and errors.

### Source excerpt

You're investigating checkout errors when someone asks who's coordinating the incident. Support needs an update, and another responder is looking for the runbook. You stop what you're doing to get everyone pointed in the same direction. They're all reasonable requests, but each one takes your attention away from understanding the problem. Yes, your team has a process for handling incidents, but carrying it out is another job for someone who's already busy. Grafana Workflows, available in public preview, turns your team's processes into automated steps across Grafana Cloud and your other tools. You can even include Grafana Assistant in those steps to investigate an issue, summarize findings, or draft an update. For example, a workflow can create an incident channel, page support according to your team's rules, and ask Assistant to prepare a briefing from the available evidence. The same approach works with your typical day-to-day operations. Once you define the workflow, Grafana Cloud can prepare the next engineer's handoff or gather the findings for your weekly service review. You decide what should happen consistently and where AI can help make sense of changing information. Get the incident response moving To illustrate how your team can benefit from Workflows, let's walk through a major incident response process. For starters, your team needs a place to collaborate and someone to coordinate the response. A runbook helps, but someone still has to find the on-call commander, open the channel, and share the right links. Workflows include blueprints, prebuilt templates you can adapt to your team's process. For this type of project, you'd start with the major incident kickoff blueprint, which can automatically respond to an active critical incident in Grafana Cloud IRM, including an incident that has just been escalated to critical. It creates a linked Slack channel, looks up your incident commander schedule, and assigns an on-call commander. It also posts your respon

## Full-stack observability in Grafana Cloud: More connections, richer context, and faster investigations for users and agents

DevFeed: [Full-stack observability in Grafana Cloud: More connections, richer context, and faster investigations for users and agents](<https://devfeed.tech/articles/full-stack-observability-in-grafana-cloud-more-connections-richer-context-and-faster-investigations-for-users-and-agents-91082.md>)

Original publisher: [Read original article](<https://grafana.com/blog/full-stack-observability-with-knowledge-graph/>)

Author: Sarah Constant

Published: 2026-10-20T16:30:02Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [applications](<https://devfeed.tech/tags/applications.md>), [but](<https://devfeed.tech/tags/but.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [context](<https://devfeed.tech/tags/context.md>), [faster](<https://devfeed.tech/tags/faster.md>), [full](<https://devfeed.tech/tags/full.md>), [full-stack](<https://devfeed.tech/tags/full-stack.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [stack](<https://devfeed.tech/tags/stack.md>), [traces](<https://devfeed.tech/tags/traces.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Grafana Cloud is expanding its Knowledge Graph to connect telemetry, infrastructure, service ownership, on-call schedules, runbooks, and lessons extracted from incident investigations, giving engineers and AI agents shared system context for troubleshooting. More Google Cloud, AWS, and Azure resources, custom entities and relationships, Knowledge Graph mode in Grafana Assistant, and runtime context for agents are generally available. The Grafana Cloud Service Center and IRM integrations are in private preview. Agents can query graph relationships and health directly with a Cypher tool; the excerpt describes this as helping investigations reach root causes faster, including a reported LexisNexis case. Some changes may require admin access.

### Source excerpt

Most teams have telemetry from across their stack, but connecting those signals to understand what's happening and how it affects users isn't always easy. Critical context about service dependencies, ownership, and past incidents often lives across tools, runbooks, and conversations between team members. That's why, today at ObservabilityCON 2026, we're announcing new capabilities that advance full-stack observability across Grafana Cloud. Powering this experience is the Knowledge Graph, the runtime context layer in Grafana Cloud that brings together your system's components, their relationships, and health insights in one connected view. We're expanding the Knowledge Graph to cover more infrastructure, applications, and user-facing signals, along with a broader range of operational context, including your service catalog, the teams on call, and lessons captured during past incidents. Together, these connections give people and AI agents the same shared context, built on open standards, about how a system fits together, helping them to troubleshoot and find root causes faster. "We've found that the hardest part of an investigation is rarely a lack of data. The challenge is connecting service ownership, dependencies, operational knowledge, and customer impact across a complex ecosystem," said Neil Wilson, Senior Director of Software Engineering at LexisNexis Risk Solutions. "Entity graph relationships [on the Knowledge Graph] help make those connections visible, giving engineers and AI systems the context they need to move from data to understanding to action." Think of Grafana Cloud as your SRE specialist: whether you work with Grafana Assistant or bring your own agent through gcx, you want that specialized expertise available when you need it, without spending the first half of an investigation reconstructing how everything fits together. That's where we're taking full-stack observability: towards faster, more reliable, and more cost-effective answers, powered by t

## Expand what's possible with Grafana: The Grafana Marketplace is now generally available

DevFeed: [Expand what's possible with Grafana: The Grafana Marketplace is now generally available](<https://devfeed.tech/articles/expand-what-s-possible-with-grafana-the-grafana-marketplace-is-now-generally-available-91085.md>)

Original publisher: [Read original article](<https://grafana.com/blog/grafana-marketplace/>)

Author: Sofia Neroda

Published: 2026-10-20T16:30:02Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [apps](<https://devfeed.tech/tags/apps.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cloud-cost-optimization](<https://devfeed.tech/tags/cloud-cost-optimization.md>), [days](<https://devfeed.tech/tags/days.md>), [developers](<https://devfeed.tech/tags/developers.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [marketplace](<https://devfeed.tech/tags/marketplace.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [pilot](<https://devfeed.tech/tags/pilot.md>), [platform](<https://devfeed.tech/tags/platform.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [revenue](<https://devfeed.tech/tags/revenue.md>), [security](<https://devfeed.tech/tags/security.md>), [sources](<https://devfeed.tech/tags/sources.md>), [support](<https://devfeed.tech/tags/support.md>), [systems-integrators](<https://devfeed.tech/tags/systems-integrators.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

The Grafana Marketplace is generally available, offering more than 30 paid, partner-backed plugins alongside the existing catalog of over 300 plugins. Partners can earn revenue to fund ongoing development and support; paid listings promise updates and support, while free community and open source plugins remain available. Marketplace plugins run in users' Grafana instances, and Grafana Labs reviews listings and requires cryptographic signing and encryption of sensitive data. Partners must remediate critical vulnerabilities within seven days and high-severity ones within 30 days, and maintain compatibility with supported Grafana versions. Grafana Labs handles billing, but partners provide plugin support. Each plugin includes a 14-day free trial for Grafana Cloud users; contracted customers are directed to arrange trials through their account team.

### Source excerpt

Earlier this year, we launched the Grafana Marketplace, a platform that gives independent software vendors, systems integrators, and developers in the Grafana community a new way to sell and distribute plugins built for Grafana. The Marketplace builds on our existing plugin catalog by enabling third-party partners and developers to earn revenue from their plugins and invest further in their development. For end users, these paid Marketplace plugins come with guarantees for ongoing updates and support, helping ensure the integrations you rely on remain secure and reliable over time. Since launching the pilot program in April, the Marketplace has grown to include more than 30 custom, partner-backed plugins for high-demand data sources and apps, ranging from cloud cost optimization tools to security solutions from Rubrik and Cisco. Today at ObservabilityCON 2026, we're excited to share that the Grafana Marketplace is generally available. And to make it easier to explore, any Grafana Cloud user can now trial Marketplace plugins free for 14 days. Why the Marketplace matters The Grafana plugin catalog includes more than 300 plugins built and maintained by Grafana Labs, our partners, and the community. This ecosystem gives users more ways to connect Grafana to the tools and data sources they rely on, while giving developers the freedom to extend Grafana for new use cases. We want developers to be inspired to keep building on Grafana, while our users have more options for monitoring their infrastructure and managing their Grafana instances, including apps and data sources for specialized use cases. But building and maintaining a production-grade plugin takes a lot of work. Until recently, independent developers and systems integrators had no direct way to fund that work through the Grafana plugin ecosystem. The Marketplace introduced that commercial model. By giving partners a way to earn revenue from their plugins, they can invest in ongoing development and support while b

## Grafana Pages: Turn data into interactive experiences with the next evolution of Grafana

DevFeed: [Grafana Pages: Turn data into interactive experiences with the next evolution of Grafana](<https://devfeed.tech/articles/grafana-pages-turn-data-into-interactive-experiences-with-the-next-evolution-of-grafana-91084.md>)

Original publisher: [Read original article](<https://grafana.com/blog/grafana-ai-next-gen-visualization/>)

Author: Maurice Rochau

Published: 2026-10-20T16:30:02Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [AI for interactive applications](<https://devfeed.tech/topics/ai-for-interactive-applications.md>), [Grafana Cloud Metrics](<https://devfeed.tech/topics/grafana-cloud-metrics.md>), [interactive storytelling](<https://devfeed.tech/topics/interactive-storytelling.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [canvas](<https://devfeed.tech/tags/canvas.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [pages](<https://devfeed.tech/tags/pages.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [question](<https://devfeed.tech/tags/question.md>), [service](<https://devfeed.tech/tags/service.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Pages is a public-preview Grafana Cloud feature for building shareable interactive apps through Grafana Assistant using existing Grafana data connections. Unlike fixed-grid dashboards, Pages can be refined conversationally and include filters, time-range controls, and drilldowns so teammates can investigate details themselves. Each page retains the queries behind its charts and numbers; users can open a source in Explore mode and compare results over the same time range. Existing Grafana permissions and data source policies apply, and actions such as Slack messages or HTTP requests show their destination and values for review before running. Examples include service triage, SLO health, Kubernetes rightsizing, alert audits, live review slides, and data-driven visualizations or games. The suggested workflow is to choose a recurring reporting task, describe the desired page to Assistant, verify representative values against sources, then refine it with users.

### Source excerpt

Teams often spend as much time preparing information as discussing it: gathering charts, checking business reports, and finding the GitHub activity that explains a change. Every follow-up question can lead to yet another round of work. That's why, as part of ObservabilityCON 2026, we're excited to introduce Grafana Pages, a new feature in Grafana Cloud that gives you a canvas to describe what you need and build a live app in minutes, based on your real data, context, and interactions. From new types of visualizations to slides and even to games, the only limitation is your imagination. With Pages, currently in public preview, you can create interactive views and tools with Grafana Assistant, using the data you already access through Grafana. There's no code and no setup; no export, upload, or deploy steps. Unlike standard dashboards, which are fixed grids of panels, you simply describe what you need, refine it through conversation, and share it with your team to explore and return to as needed. What Pages unlocks Pages let you build trusted, reliable, and scalable (mini) apps in the environment you know and use with Grafana Assistant by your side. Oftentimes, broad solutions might miss a use case that's specific to your organization. But with Pages you can easily build and own your own information hub, whether it's an incident view, a runbook, a deploy tracker, an exec readout, or a customer-facing status page. Let's look at some ways you can build Pages today. Build on your existing data connections Getting an internal tool working starts with connecting it to useful data. Pages builds on the data connections you already use in Grafana, giving you a starting point for bringing operational and business information together. Put transaction volumes beside service performance, or build a release review around production trends and relevant connected context. Spend your effort shaping the experience around the question your team needs to answer, rather than getting bog

## ObservabilityCON 2026: A guide to all the announcements from Grafana Labs

DevFeed: [ObservabilityCON 2026: A guide to all the announcements from Grafana Labs](<https://devfeed.tech/articles/observabilitycon-2026-a-guide-to-all-the-announcements-from-grafana-labs-91086.md>)

Original publisher: [Read original article](<https://grafana.com/blog/observabilitycon-2026-announcements/>)

Author: Grafana Labs Team

Published: 2026-10-20T16:30:02Z

Content type: news

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>), [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-observability](<https://devfeed.tech/tags/agentic-observability.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [assistant-investigations](<https://devfeed.tech/tags/assistant-investigations.md>), [assistant-watchers](<https://devfeed.tech/tags/assistant-watchers.md>), [automation](<https://devfeed.tech/tags/automation.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [context](<https://devfeed.tech/tags/context.md>), [control](<https://devfeed.tech/tags/control.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-labs](<https://devfeed.tech/tags/grafana-labs.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Labs announced Grafana Cloud updates spanning AI operations, telemetry cost and query performance, system context, user experience, and workflow automation. Assistant Watchers are generally available and detect changes against historical telemetry baselines; Managed Sandboxes and Pages are in public preview, with proposed code changes requiring human review. Adaptive Metrics auto-apply is generally available with a cost-first safeguard, while Adaptive Logs Archive is in public preview and trace retrieval for traces dropped by Adaptive Traces is generally available. New sampling options aim to preserve service and attribute diversity. Logline-based full-text search is generally available at no added cost; a customer example reports searching about 100 GB in under three seconds versus nearly a terabyte in three minutes. Knowledge Graph additions connect cloud resources and operational context, with some integrations still in preview. Session Replay and Grafana Workflows are in public preview; mobile observability and critical user journeys are in private preview. The excerpt presents these as announcements and examples, not independent evaluations.

### Source excerpt

Today at ObservabilityCON 2026 in San Francisco, we unveiled a range of new Grafana Cloud capabilities designed to reshape cloud economics, bring richer context and deeper visibility across your systems and end-user experiences, and help teams move toward autonomous operations. Check out the keynote to learn more about the latest updates to the open agentic observability cloud, and read on for a quick recap of all the news from ObservabilityCON 2026. Autonomous operations with the help of AI With Grafana Assistant in Grafana Cloud, you can bring more of your operational tasks together in one place so you can resolve incidents faster and get back to building. And you're doing it with AI features that automate much of the undifferentiated heavy lifting while still keeping you in control. Assistant Investigations, generally available since late July, lets you run longer, deeper investigations that can start automatically from an alert or incident, and teams can run them from the platform, Slack, the Grafana Cloud MCP server, or gcx. And today we're adding new AI features to help you take your automation even further: Assistant Watchers (now generally available) are always-on agents that detect changes not captured by predefined alert rules. You describe what to monitor in plain language and select the relevant data sources. Your watcher then establishes a baseline from historical telemetry patterns and surfaces findings when those patterns change. Grafana Managed Sandboxes (public preview) gives you a controlled cloud environment to ask questions about source code, make changes, and prepare pull requests from conversations in Grafana Cloud. It uses context from your repository code and live telemetry to propose potential fixes within a sandbox environment that a person on your team can then review and approve. Grafana Pages (public preview) lets you build visualizations beyond any fixed constraints, making them closer to an app than a dashboard. You describe what you n

## From production problem to proposed fix: Implement autonomous operations with Grafana AI

DevFeed: [From production problem to proposed fix: Implement autonomous operations with Grafana AI](<https://devfeed.tech/articles/from-production-problem-to-proposed-fix-implement-autonomous-operations-with-grafana-ai-91083.md>)

Original publisher: [Read original article](<https://grafana.com/blog/grafana-ai-autonomous-operations/>)

Author: Maurice Rochau

Published: 2026-10-20T16:30:02Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [assistant-investigations](<https://devfeed.tech/tags/assistant-investigations.md>), [assistant-watchers](<https://devfeed.tech/tags/assistant-watchers.md>), [automate](<https://devfeed.tech/tags/automate.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [errors](<https://devfeed.tech/tags/errors.md>), [features](<https://devfeed.tech/tags/features.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [operations](<https://devfeed.tech/tags/operations.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Assistant combines recurring service checks, incident investigation, and proposed code changes while leaving production decisions to the team. Watchers use selected data sources and historical telemetry to establish baselines, periodically assess signals, and report evidence; critical findings can trigger Investigations. Investigations explore metrics, logs, traces, and profiles, test hypotheses, and provide supporting queries for responders to inspect and guide. With a repository connected and coding enabled, Managed Sandboxes can use repository code and live telemetry to prepare changes and run available checks in a controlled cloud environment, potentially producing a proposed pull request for review. Existing alerts remain responsible for dependable paging, and passing tests do not replace confirming recovery in production. The article recommends starting with a familiar service and bounded task, calibrating checks, reviewing findings, then expanding delegated work as results build confidence. Watchers and Investigations are generally available; Managed Sandboxes is in public preview.

### Source excerpt

You've just finished a deployment, and though your service is up, you start to notice some requests are getting slower. To address the lag, someone--or, more likely, some group of people on your team--needs to watch the dashboards, decide whether the change matters, investigate what happened, and turn the findings into a fix. At each step you're gathering context--and often explaining that context again to the next person or tool. To make matters worse for the team responsible for the service, all this work is getting in the way of everything else they need to build. With Grafana Assistant in Grafana Cloud, you can bring more of those tasks together in one place, helping you resolve incidents faster so you can get back to building. And you're doing it with AI features that automate much of the undifferentiated heavy lifting while still keeping you in control. Assistant Watchers (generally available today as part of ObservabilityCON 2026) provides ongoing attention to the conditions you care about. Assistant Investigations (generally available) gathers evidence about what changed. And Grafana Managed Sandboxes (public preview as of today) uses that context to prepare changes in a controlled cloud environment, giving your team something concrete to review. In this blog post, I'll show you how you can use these features collectively for better observability outcomes. Give the service ongoing attention Consider a checkout service after a release. You want to know whether customers are encountering sustained errors or slower responses, while also accounting for the brief disruption you expect during deployment. With Watchers, our always-on agents, you describe that concern and select the relevant data sources. Assistant then analyzes your historical telemetry to establish a baseline and calibrate the checks. From there, the watcher periodically assesses those signals and provides reporting along with the evidence behind its findings. If a watcher finds a critical issue, it

## Break the link between data volume and your observability bill with Adaptive Telemetry

DevFeed: [Break the link between data volume and your observability bill with Adaptive Telemetry](<https://devfeed.tech/articles/break-the-link-between-data-volume-and-your-observability-bill-with-adaptive-telemetry-91081.md>)

Original publisher: [Read original article](<https://grafana.com/blog/cut-costs-keep-what-you-need-adaptive-telemetry/>)

Author: JK Basra

Published: 2026-10-20T16:30:02Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [adaptive-telemetry](<https://devfeed.tech/tags/adaptive-telemetry.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [sampling](<https://devfeed.tech/tags/sampling.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Adaptive Telemetry aims to reduce observability costs by retaining or indexing data based on its value. For traces, volumetric sampling allocates samples across services and request types as traffic changes; Grafana Labs reports about 25% higher information density than probabilistic sampling at the same volume. Diversity sampling captures unique attribute combinations every 15 minutes. Dropped traces remain retrievable by trace ID for 24 hours, but are excluded from search and aggregations. For logs, Fleet-managed Adaptive Logs filters matching lines in collectors before they leave the environment; archive stores logs in customers' low-cost object storage for replay on demand. Fleet management and archive are in public preview; replay is coming soon. Adaptive Metrics recommends lower-cardinality alternatives for unused detail, while Auto-Apply can apply new recommendations by segment, with exemptions and coverage-first or cost-first modes. Auto-Apply is generally available.

### Source excerpt

In the AI era, where telemetry is generated by every model call, tool invocation, and agent step, organizations need more help than ever when it comes to navigating the economics of observability. For a lot of teams, the default response is a "data diet" of shorter retention, which leaves services or environments out of collection, or basic sampling, which is more guesswork than strategy. Either way, you end up cutting to control the bill, and you risk losing the very data you need during an incident. Your costs shouldn't scale with how much data you ingest. Instead, they should scale with the value you get from it, so you only pay to keep the data that earns its place. That's what Adaptive Telemetry is built for, and organizations such as Rapid7 are already seeing the results. "Moving to Grafana Cloud and using Adaptive Telemetry cut our metrics costs enough to fund logs and traces as well," says Carl Eastman, Principal Software Engineer, Rapid7. "Our visibility went up while our costs went down, and dashboards and queries are faster and less noisy." You can already use Adaptive Telemetry for all your observability signals, and we're continuing to build on that foundation so you can get even more precise about which traces you keep, improve your logs economics, and get more from Adaptive Metrics with less toil. Here's how that looks in practice. Keep only the traces that matter, and cut volume by 90% Traces are where the data diet hurts most. Many teams sample with a fixed percentage, which treats a slow checkout request the same as a routine health check. Cut the percentage and your bill drops, but so does the chance that the trace you need is still there when something breaks. Adaptive Traces already handles the hard part (tail sampling) without you running a pipeline. Three newer capabilities make retention even more precise. Automatically keep your most valuable traces, without the policy toil Volumetric sampling gives you a more valuable sample than probabilis

## 6 improvements that make Grafana Assistant better at helping your workflows

DevFeed: [6 improvements that make Grafana Assistant better at helping your workflows](<https://devfeed.tech/articles/6-improvements-that-make-grafana-assistant-better-at-helping-your-workflows-90233.md>)

Original publisher: [Read original article](<https://grafana.com/blog/six-improvements-that-make-grafana-assistant-better-at-helping-your-workflows/>)

Author: Maurice Rochau

Published: 2026-10-19T18:10:01Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>)

Tags: [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana describes six efforts to improve its Assistant, including dashboard editing, agent evaluations, tool discovery, search, incident investigation, and production judging. Reported dashboarding error rates fell from 2.47% to 0.65%, 95th-percentile operation latency declined from 63 seconds to 28.8 seconds, and cost per request fell 18%. The article also discusses how evaluation and production telemetry guide agent improvements.

### Source excerpt

When you ask Grafana Assistant to build a dashboard or investigate an alert, you're doing so because there's work to be done. To do that work effectively, you need the right data, changes you can inspect, and conclusions supported by evidence. You also want Assistant to avoid mistakes and act quickly. Over the past six months, our team has worked hard to improve what makes those outcomes possible. We've changed how agents find context, discover capabilities, edit dashboards, and recover from errors. At the same time, we've built better ways to determine whether an improvement actually helps. These projects are closely connected. Better evaluations reveal where an agent struggles. Those findings guide changes to its tools and context. Production telemetry tells us whether those changes worked and where to look next. We've been documenting this work on our engineering blog, Unprompted, taking deep dives into the decisions and implementations that went into those efforts. Today, I want to share how those changes have translated to better outcomes for our users. Dashboarding: faster, prettier, less errors By mid-2026, dashboarding mode accounted for 27% of Assistant conversations. Users were also telling us exactly where it needed to work better: some operations were slow, consumed too many tokens, or changed things they should have left alone. The team started by establishing a baseline with Agent Observability and building reproducible tests. Over roughly 10 weeks, the reported dashboarding error rate fell from 2.47% to 0.65%. The 95th-percentile latency for individual operations dropped from 63 seconds to 28.8 seconds, while cost per request fell by 18%. As Dominik Broj describes in his dashboarding write-up, those results came from repeated, specific improvements. Engineers found failures in production, reproduced them as evaluation scenarios, fixed the underlying problems, and checked the results after rollout. The dashboarding test catalog grew from 78 scenarios t

## Get observability in your pocket with the Grafana mobile app

DevFeed: [Get observability in your pocket with the Grafana mobile app](<https://devfeed.tech/articles/get-observability-in-your-pocket-with-the-grafana-mobile-app-88366.md>)

Original publisher: [Read original article](<https://grafana.com/blog/get-observability-in-your-pocket-with-the-grafana-mobile-app/>)

Author: Ksenia Yadav

Published: 2026-10-15T22:39:33Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [observability](<https://devfeed.tech/topics/observability.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud-irm](<https://devfeed.tech/tags/grafana-cloud-irm.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app](<https://devfeed.tech/tags/mobile-app.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [natural-language](<https://devfeed.tech/tags/natural-language.md>), [observability](<https://devfeed.tech/tags/observability.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

The Grafana mobile app adds Grafana Assistant, dashboards, and incident investigation features to its existing alerts, incidents, and on-call notifications. The article describes using its context-aware assistant to ask questions, inspect dashboards, and begin investigations on a phone, then continue the same work in Grafana's web interface.

### Source excerpt

When you're on the go, your phone is often the only observability tool you have. And what you can do with it in the first few minutes matters. With the incredible innovation that has gone into mobile CPUs, GPUs and displays, a phone is a powerful device where you can immediately see what's happening and start acting on it. And the Grafana mobile app now allows you to both see and act. The app (available for Android and iOS) has always been good at notifying you of what's happening--alerts, incidents, and on-call schedules, previously under the Grafana IRM name. Now you can also ask questions in natural language, view your dashboards, and take actions across your stack. It is not a smaller, more cramped version of your computer, but a powerful starting point for the first few minutes of an incident. Grafana Assistant on your phone Grafana Assistant is a context-aware agent that can answer questions and take action across your stack. It already lives where you work: as a sidebar chat in the Grafana web UI, in Workspace if you prefer a conversation-focused experience for Grafana, in Slack or Microsoft Teams, or through gcx on the command line. It now runs on your phone, too, with the same conversations and the same abilities. What makes Assistant useful is that it never starts from zero. It knows which stack you're in, which dashboard or alert you're looking at, and how your data is shaped. With Assistant on your phone, you can: Understand alerts and incidents: Catch up on what's happened, explore what changed, and check whether a problem has occurred before. Find relevant dashboards: Ask which dashboards can help you understand an issue and open them right from the conversation. Check your on-call schedule: Find out when you're on rotation without hunting through schedules. Launch an investigation: Get Assistant working on a complex issue before you reach your laptop. Pick up where you left off: Continue the same conversation on your computer, with the context intact.

## Coverage-first or cost-first: two ways to automatically apply Adaptive Metrics' recommendations

DevFeed: [Coverage-first or cost-first: two ways to automatically apply Adaptive Metrics' recommendations](<https://devfeed.tech/articles/coverage-first-or-cost-first-two-ways-to-automatically-apply-adaptive-metrics-recommendations-88002.md>)

Original publisher: [Read original article](<https://grafana.com/blog/coverage-first-or-cost-first-two-ways-to-automatically-apply-adaptive-metrics-recommendations/>)

Author: Arun Ulagappan

Published: 2026-10-15T13:50:51Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>)

Tags: [adaptive-metrics](<https://devfeed.tech/tags/adaptive-metrics.md>), [adaptive-telemetry](<https://devfeed.tech/tags/adaptive-telemetry.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [availability](<https://devfeed.tech/tags/availability.md>), [cost-management](<https://devfeed.tech/tags/cost-management.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana announces general availability of a second Adaptive Metrics auto-apply mode, cost-first, alongside coverage-first. Cost-first applies recommendations that reduce active metric series and limits increases so the total does not rise above its starting level for a cycle. Coverage-first applies recommendations immediately to maintain resolution for queried data, while segmented settings let teams choose a mode for different telemetry groups.

### Source excerpt

Adaptive Metrics , which is part of the Adaptive Telemetry suite, looks at how your metrics are actually used and recommends how much detail you should keep for each metric. This helps you cut costs while still retaining the data you actually need. Last year we added auto-apply capabilities that let you implement those recommendations automatically, but only with coverage-first behavior, maximizing coverage of whatever you're querying. If your team wanted anything different, the only option was to review and apply recommendations by hand. But now, with the General Availability release of auto-apply, we've added a second mode: cost-first, a built-in safeguard that only applies recommendations that won't increase your total active series--ensuring optimization never turns into a cost spike. Auto-Apply continuously applies recommendations in either mode with no human intervention, while your existing dashboards, alerts, and queries keep working unchanged. How cost-first mode decides what to apply Every recommendation Adaptive Metrics generates comes with a projected change to your series count--some recommendations decrease it, others increase it. Cost-first mode can now take those projected changes into account, much like a careful manual review would, in three steps: Series-reducing recommendations always apply. Anything that lowers your projected series count goes through immediately, including brand-new recommendations. Series-increasing recommendations get ranked. Anything that would raise your projected series count is sorted from least impactful to most impactful. Adaptive Metrics stops at your current total. It works down that ranked list, applying recommendations until the next one would push your projected series count above where it started the cycle. How coverage-first mode decides what to apply Coverage-first works more simply than cost-first does: every recommendation gets applied as soon as it's generated, whether it lowers your series count or raises it.

## Go from alert to post-incident review with Grafana Cloud IRM and AI

DevFeed: [Go from alert to post-incident review with Grafana Cloud IRM and AI](<https://devfeed.tech/articles/go-from-alert-to-post-incident-review-with-grafana-cloud-irm-and-ai-87052.md>)

Original publisher: [Read original article](<https://grafana.com/blog/go-from-alert-to-post-incident-review-with-grafana-cloud-irm-and-ai/>)

Author: Ashley Somerville

Published: 2026-10-14T17:39:29Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud-irm](<https://devfeed.tech/tags/grafana-cloud-irm.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [post-incident-review](<https://devfeed.tech/tags/post-incident-review.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

The article walks through using Grafana Cloud IRM and Grafana Assistant to manage a software incident from alert through investigation and post-incident review. It describes how incident context, team coordination, AI-generated hypotheses, and review materials are connected across Slack, mobile, and other tools.

### Source excerpt

You've got 10 minutes before your next meeting when your phone starts ringing. You're being paged because the frontend is erroring with failed API requests. You open one tool to see what fired, then another to figure out what's going on. You message a teammate in Slack to see if they're noticing the same thing. That's a lot of context switching, and it's still how a lot of teams' incident response works today. Opening another tool and catching someone up takes time. Details can get lost when you manually copy context from one place to another. It doesn't have to be this way. With Grafana Cloud IRM, you get on-call support, incident management, chatops in Slack or Microsoft Teams, investigations, and the Grafana mobile app, all connected through the incident record. Let's follow the frontend incident from the first page through the response and post-incident review to illustrate how your team can start improving their processes today. The page already has context When you get paged, you need to understand how serious the problem is and what to check first. With IRM, you're starting with more than an alert name. When you open the alert group, it shows the affected service, the dashboard panel tied to the alert, its history, and how many individual alerts were folded into the page. Imagine the difference between "the frontend is exposing API errors" and "the frontend is exposing HTTP 500 errors from the adService, the issue has already flapped twice in 24 hours, and three related alerts are firing in the same alert group." Figuring out what else is affected Next, you need to figure out whether the frontend errors are isolated or part of something bigger, and whether the platform team is getting paged, too. A lot of teams will do this by bouncing between dashboards, service maps, observability data, and Slack or Teams. From the Slack thread, you ask Grafana Assistant, "What else is firing, and how is it related?" It uses the same alert context you're looking at and post

[Next page](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md?cursor=WyIyMDI2LTEwLTE0VDE3OjM5OjI5KzAwOjAwIiwgIjBiNDVjNjNlLTE0YTktNDhjYS04NTBkLWEwMDA5MjA0ZTYzZSJd>)