# Grafana Cloud

Grafana Cloud is an OpenTelemetry-native observability platform that combines observability, incident response, and AI-powered workflows.

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

## 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

## 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

## 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

## 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

## Datadog vs. Grafana: Comparing Two Paths to Observability (2026)

DevFeed: [Datadog vs. Grafana: Comparing Two Paths to Observability (2026)](<https://devfeed.tech/articles/datadog-vs-grafana-comparing-two-paths-to-observability-2026-97280.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/observability/datadog-vs-grafana>)

Author: John Blust

Published: 2026-10-23T09:06:09.935733Z

Content type: comparison

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana Cloud Metrics](<https://devfeed.tech/topics/grafana-cloud-metrics.md>), [datadog agent](<https://devfeed.tech/topics/datadog-agent.md>), [tracing](<https://devfeed.tech/topics/tracing.md>)

Tags: [2020](<https://devfeed.tech/tags/2020.md>), [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-machine-learning](<https://devfeed.tech/tags/ai-and-machine-learning.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-investigations](<https://devfeed.tech/tags/ai-assisted-investigations.md>), [ai-engine](<https://devfeed.tech/tags/ai-engine.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cost](<https://devfeed.tech/tags/cost.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [devops](<https://devfeed.tech/tags/devops.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operational](<https://devfeed.tech/tags/operational.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [platform](<https://devfeed.tech/tags/platform.md>), [scope](<https://devfeed.tech/tags/scope.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

Datadog simplifies operations with a fully managed SaaS platform, while Grafana offers managed Grafana Cloud or a self-hosted Loki, Grafana, Tempo, and Mimir stack that gives teams control but requires ongoing work to scale, upgrade, and maintain availability. Telemetry growth can make Datadog custom metric allowances and Grafana Cloud active-series usage costs harder to predict; self-hosting shifts those costs to infrastructure and engineering. Both offer AI-assisted analysis: Datadog integrates Watchdog across its products, while Grafana Cloud combines machine learning and investigations with its composable ecosystem. The article presents New Relic as another managed option, supporting OpenTelemetry, Prometheus, and Grafana dashboards; it prices by ingested data and user seats, with 100 GB monthly ingest included per account.

### Source excerpt

Datadog vs. Grafana compared on cost predictability, operational overhead, and observability scope, and where a unified platform changes the calculus.

## 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

## Grafana Labs connects observability and incident response with Knowledge Graph

DevFeed: [Grafana Labs connects observability and incident response with Knowledge Graph](<https://devfeed.tech/articles/grafana-labs-connects-observability-and-incident-response-with-knowledge-graph-92557.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/21/grafana-labs-knowledge-graph/>)

Author: Industry News

Published: 2026-10-21T09:30:38Z

Content type: release

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [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>), [incident](<https://devfeed.tech/topics/incident.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [база знаний](<https://devfeed.tech/topics/tag-c51cc4bf76e5.md>), [knowledge-management](<https://devfeed.tech/topics/knowledge-management.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Grafana Cloud Frontend Observability](<https://devfeed.tech/topics/grafana-cloud-frontend-observability.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [context](<https://devfeed.tech/tags/context.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [digital-experience](<https://devfeed.tech/tags/digital-experience.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-labs](<https://devfeed.tech/tags/grafana-labs.md>), [graph](<https://devfeed.tech/tags/graph.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [industry-news](<https://devfeed.tech/tags/industry-news.md>), [knowledge-graph](<https://devfeed.tech/tags/knowledge-graph.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Grafana Labs is adding a Knowledge Graph to every Grafana Cloud stack to connect telemetry across infrastructure, applications and user experience, giving responders and agents shared runtime context for tracing dependencies and business impact. Custom entities and agent access are generally available; service ownership and runbooks in the graph are in private preview. Digital Experience Monitoring adds Session Replay (public preview), mobile observability and Critical User Journeys (private previews), linking browser or mobile experience to stack telemetry. Grafana Cloud IRM adds event-driven Workflows (public preview), plus private-preview Operational Context that retains prior investigation findings and a Response Console for people and agents to collaborate. The excerpt describes the announcements and availability stages, not measured outcomes.

### Source excerpt

Grafana Labs has announced a Knowledge Graph in every Grafana Cloud stack, alongside new Digital Experience Monitoring capabilities and updates to Grafana Cloud Incident Response Management (IRM). The releases connect infrastructure and application dependencies with user experience and incident response, giving people and agents shared context to investigate problems and take action. As agentic systems become more architecturally complex and teams use agents to investigate and respond to problems, those agents need context that connects ... More -> The post Grafana Labs connects observability and incident response with Knowledge Graph appeared first on Help Net Security.

## Grafana Labs leans on AI agents to automate AI agent observability

DevFeed: [Grafana Labs leans on AI agents to automate AI agent observability](<https://devfeed.tech/articles/grafana-labs-leans-on-ai-agents-to-automate-ai-agent-observability-90876.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/20/grafana-labs-leans-on-ai-agents-to-automate-ai-agent-observability/>)

Author: Mike Wheatley

Published: 2026-10-20T17:00:41Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [observability ai agents](<https://devfeed.tech/topics/observability-ai-agents.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [adaptive-logs-archive](<https://devfeed.tech/tags/adaptive-logs-archive.md>), [adaptive-telemetry](<https://devfeed.tech/tags/adaptive-telemetry.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [ai-agent-observability](<https://devfeed.tech/tags/ai-agent-observability.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-monitoring](<https://devfeed.tech/tags/ai-monitoring.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [assistant-watchers](<https://devfeed.tech/tags/assistant-watchers.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-agents](<https://devfeed.tech/tags/cloud-agents.md>), [grafana-assistant](<https://devfeed.tech/tags/grafana-assistant.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-cloud-agents](<https://devfeed.tech/tags/grafana-cloud-agents.md>), [grafana-cloud-logs](<https://devfeed.tech/tags/grafana-cloud-logs.md>), [grafana-labs](<https://devfeed.tech/tags/grafana-labs.md>), [knowledge-graph](<https://devfeed.tech/tags/knowledge-graph.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observability-stack](<https://devfeed.tech/tags/observability-stack.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

Grafana Cloud is adding agents and telemetry features to monitor AI workloads and help investigate and remediate issues. Assistant Watchers are always-on agents that learn typical telemetry patterns and flag anomalies; Grafana Cloud Agents, available in preview, analyze code alongside production behavior and prepare fixes for human review. Grafana treats agent sessions and LLM conversations as telemetry alongside conventional logs, metrics, and traces. Other updates include Pages for custom AI workload visualizations; faster full-text search across low-frequency logs at no additional cost; Adaptive Logs Archive, which routes logs to customer object storage in open formats for lower-cost retention; and Knowledge Graph, linking infrastructure and application dependencies to user experience. Mobile Observability and Session Replay add a user perspective. The article presents these as a workflow for detection, diagnosis, and proposed action, with human review of fixes.

### Source excerpt

Observability software pioneer Grafana Labs Inc. is flexing its muscles in the rapidly emerging market for artificial intelligence monitoring tools with a swath of updates to its Grafana Cloud platform announced at ObservabilityCON 2026 today. The startup announced a new suite of AI agents, including Assistant Watchers for monitoring AI workloads and autonomous agents, and [...] The post Grafana Labs leans on AI agents to automate AI agent observability appeared first on SiliconANGLE.

## 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

## 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.

## 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

## Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud

DevFeed: [Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud](<https://devfeed.tech/articles/manage-your-opentelemetry-collectors-with-fleet-management-in-grafana-cloud-77315.md>)

Original publisher: [Read original article](<https://grafana.com/blog/manage-your-opentelemetry-collectors-with-fleet-management-in-grafana-cloud/>)

Author: Marko Bachvarovski

Published: 2026-10-08T14:04:56Z

Content type: article

Language: en

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

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

Tags: [analytics](<https://devfeed.tech/tags/analytics.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>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.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>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [telemetry-pipelines](<https://devfeed.tech/tags/telemetry-pipelines.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud Fleet Management now supports supported upstream OpenTelemetry Collector distributions through OpAMP, allowing teams to centrally manage collectors without migrating to Grafana Alloy. The article describes targeting YAML pipelines across collector fleets, Terraform-based configuration and enrollment, automatic monitoring, and configuration merging for reusable pipelines. It also explains how the gateway pattern can separate edge collection from shared processing.

### Source excerpt

If you've built your telemetry pipelines around OpenTelemetry Collectors, you've already invested in a collector distribution, YAML configuration, and a deployment model that fits your infrastructure. As that deployment grows, managing it means keeping shared configuration consistent, accommodating different workloads, and understanding whether your collectors are healthy. Fleet Management in Grafana Cloud brings those tasks together in one place. With support for the Open Agent Management Protocol (OpAMP) now generally available, you can bring supported OpenTelemetry Collector distributions into Fleet Management while continuing to use the OTel configuration language and components you already know. We started with Grafana Alloy, Grafana's distribution of the OpenTelemetry Collector. OpAMP support extends that management workflow to organizations running upstream OTel Collector distributions, so you can adopt centralized management without first migrating to Alloy. Keep your OTel configuration, manage it across your fleet For a platform team supporting multiple services or environments, collector configuration often includes both shared policies and workload-specific requirements. You might apply common processing across your fleet while enabling additional collection pipelines only for particular teams, services, or environments. Fleet Management lets you define those pipelines in OTel YAML and match them to the collectors that should run them. You can update a shared pipeline centrally and apply it across the matching collectors, reducing the work of maintaining configuration separately for each deployment. For teams using infrastructure as code, Terraform support brings this workflow into your existing processes. You can create pipelines with YAML configuration and register active collectors with Fleet Management, making configuration and enrollment part of a repeatable, version-controlled workflow. You also get visibility into the collectors running those pipel

## Manage synthetic checks at scale: Introducing folders in Grafana Cloud Synthetic Monitoring

DevFeed: [Manage synthetic checks at scale: Introducing folders in Grafana Cloud Synthetic Monitoring](<https://devfeed.tech/articles/manage-synthetic-checks-at-scale-introducing-folders-in-grafana-cloud-synthetic-monitoring-66834.md>)

Original publisher: [Read original article](<https://grafana.com/blog/manage-synthetic-checks-at-scale-introducing-folders-in-grafana-cloud-synthetic-monitoring/>)

Author: Virginia Cepeda

Published: 2026-10-07T15:00:41Z

Content type: release

Language: en

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

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

Tags: [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>), [reliability](<https://devfeed.tech/tags/reliability.md>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud Synthetic Monitoring folders, now generally available, let teams group checks by service, environment, or team; manage checks in batches; and control access through folder permissions. Folders are supported in the UI, API, and Terraform, where moving a managed check in the UI can produce configuration drift.

### Source excerpt

As your use of Grafana Cloud Synthetic Monitoring grows, so does the number of checks you need to manage across services, environments, and teams. Eventually, a single flat list of checks becomes difficult to navigate, and even simple questions get harder to answer: Which checks belong to the payments team? Can I disable everything in staging during a maintenance window? Who should be able to edit the checks for this service? Synthetic Monitoring folders, now generally available, help solve this challenge. You can organize checks into the same Grafana Cloud folders you already use for dashboards and alert rules, making it easier to group checks by team, service, or environment, manage multiple checks at once, and control who can edit them. The benefits of folders in Synthetic Monitoring Grafana Cloud Synthetic Monitoring is a black box monitoring solution that lets you proactively assess system reliability and performance by running checks from probe locations around the world. You can set up different types of checks, including ping checks, browser checks, scripted checks, DNS checks, and HTTP checks, to verify system performance at various network levels. But as your Synthetic Monitoring setup grows, the process of managing checks one at a time doesn't scale. You could have dozens of checks for the same service, separate sets for production and staging, or hundreds of checks owned by different teams. Without a way to group them, finding the right checks, making changes across them, and keeping ownership clear all require more manual work. Folders give you a way to manage checks in a way that aligns with how your organization already works. Group checks by team, service, environment, or another structure that makes sense for you, then use that grouping to navigate your checks, take action across them, and control access. Because Synthetic Monitoring uses standard Grafana Cloud folders, the same organizational structure you use for dashboards and alert rules can now

## Stop rewriting the same update with AI-Powered Incident Communications by Cristina Dias

DevFeed: [Stop rewriting the same update with AI-Powered Incident Communications by Cristina Dias](<https://devfeed.tech/articles/stop-rewriting-the-same-update-with-ai-powered-incident-communications-by-cristina-dias-82844.md>)

Original publisher: [Read original article](<https://www.pagerduty.com/blog/chatops/stop-rewriting-the-same-update-with-ai-powered-incident-communications/>)

Author: Cristina Dias

Published: 2026-10-07T11:30:46Z

Content type: article

Language: en

Sources: [PagerDuty](<https://devfeed.tech/sources/pagerduty.md>)

Topics: [incident management](<https://devfeed.tech/topics/incident-management.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Heroku AI](<https://devfeed.tech/topics/heroku-ai.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [chatops](<https://devfeed.tech/tags/chatops.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [customer-service](<https://devfeed.tech/tags/customer-service.md>), [incident-management-response](<https://devfeed.tech/tags/incident-management-response.md>), [pagerduty](<https://devfeed.tech/tags/pagerduty.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

PagerDuty describes AI-Powered Incident Communications, which uses agents to capture incident bridge audio and chat, draft internal and customer status updates, and present them in Slack for responder review and publication. It also sends periodic updates to incident channels and feeds captured context into post-incident reviews and SRE Agent memory.

### Source excerpt

This blog post is part of PagerDuty's ongoing series on how we're helping customers navigate their journey towards autonomous operations. Read on to learn about... The post Stop rewriting the same update with AI-Powered Incident Communications appeared first on PagerDuty.

## Introducing AI Observability for OpenTelemetry

DevFeed: [Introducing AI Observability for OpenTelemetry](<https://devfeed.tech/articles/introducing-ai-observability-for-opentelemetry-78515.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/news/introducing-ai-observability-for-opentelemetry>)

Author: David Fabritius

Published: 2026-10-06T12:00:00Z

Content type: release

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-monitoring](<https://devfeed.tech/tags/ai-monitoring.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [aiops](<https://devfeed.tech/tags/aiops.md>), [costs](<https://devfeed.tech/tags/costs.md>), [devops](<https://devfeed.tech/tags/devops.md>), [new-relic](<https://devfeed.tech/tags/new-relic.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [shadow-ai](<https://devfeed.tech/tags/shadow-ai.md>)

### AI overview

New Relic introduces AI Observability for OpenTelemetry, combining OpenTelemetry GenAI telemetry with native APM data. The article describes model inventories and cost, latency, and error tracking; runtime normalization without duplicating telemetry; automatic discovery of AI services; and evaluation safeguards for prompt injection, PII exposure, and toxic outputs.

### Source excerpt

Unify OpenTelemetry AI with New Relic. Track token costs, discover shadow AI, and block prompt injections in real time without data duplication.

## Grafana Turns Cypress Test Results Into Persistent Observability Data

DevFeed: [Grafana Turns Cypress Test Results Into Persistent Observability Data](<https://devfeed.tech/articles/grafana-turns-cypress-test-results-into-persistent-observability-data-59806.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/grafana-cypress-observability/>)

Author: Craig Risi

Published: 2026-09-25T12:00:00Z

Content type: tutorial

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Cypress](<https://devfeed.tech/topics/cypress.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [devops](<https://devfeed.tech/tags/devops.md>), [flaky-tests](<https://devfeed.tech/tags/flaky-tests.md>), [github-actions](<https://devfeed.tech/tags/github-actions.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>), [grafana-cypress-observability](<https://devfeed.tech/tags/grafana-cypress-observability.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>)

### AI overview

Grafana Labs describes a practical method for turning Cypress test results into Prometheus metrics and sending them to Grafana Cloud. Using Cypress lifecycle hooks, Pushgateway, and Grafana Alloy, teams can track failures, durations, flaky tests, and longer-term quality trends alongside application and infrastructure telemetry.

### Source excerpt

Grafana Labs has published a practical approach for monitoring Cypress test suites by converting test results into Prometheus metrics and sending them to Grafana Cloud. By Craig Risi

## Digital Experience Monitoring with Grafana Cloud: Session Replay, synthetic checks, and faster investigations

DevFeed: [Digital Experience Monitoring with Grafana Cloud: Session Replay, synthetic checks, and faster investigations](<https://devfeed.tech/articles/digital-experience-monitoring-with-grafana-cloud-session-replay-synthetic-checks-and-faster-investigations-21514.md>)

Original publisher: [Read original article](<https://grafana.com/blog/digital-experience-monitoring-with-grafana-cloud-session-replay-synthetic-checks-and-faster-investigations/>)

Author: Bukola Ayodele

Published: 2026-09-15T01:35:30.954353Z

Content type: article

Language: en

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

Topics: [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [tracing](<https://devfeed.tech/topics/tracing.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-cloud-frontend-observability](<https://devfeed.tech/tags/grafana-cloud-frontend-observability.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [javascript](<https://devfeed.tech/tags/javascript.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>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>), [session-replay](<https://devfeed.tech/tags/session-replay.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [traces](<https://devfeed.tech/tags/traces.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

This article explains how Digital Experience Monitoring in Grafana Cloud combines Frontend Observability, Synthetic Monitoring, real user monitoring, and session replay. It shows how these capabilities help engineering teams detect issues proactively, understand their scope and root causes, correlate frontend signals with backend traces, and resolve production problems faster.

### Source excerpt

When something breaks in production, the questions that matter most are also the toughest to answer from metrics alone: who was affected, what did they actually see, and is this worth waking someone up for? Answering those questions requires a fuller picture of the issue and its impact on your users. That's where Digital Experience Monitoring (DEM) in Grafana Cloud comes in. By combining Frontend Observability and Synthetic Monitoring, DEM connects real user experiences with proactive testing, helping engineering teams understand the scope of an issue, investigate its cause, and resolve it faster, all within Grafana Cloud. In this blog post, we'll walk through some of the latest DEM updates in Grafana Cloud, and how to get started. You can also learn more by watching the video below. First, what is Digital Experience Monitoring? Digital Experience Monitoring in Grafana Cloud gives you a complete picture of how users experience your web applications, from real user data to proactive synthetic checks. DEM helps your team achieve: Real user visibility: know how users truly experience your web application, not just what your backend metrics suggest. Proactive detection: catch problems before your users do, using automated checks against your critical user journeys. End-to-end correlation: connect a frontend signal to the backend trace behind it. Faster resolution: cut your mean time to recovery from hours to minutes. Session Replay: see exactly what your users saw Session Replay in Grafana Cloud Frontend Observability lets you visually replay what a user saw and did inside your web application. Your team can watch exactly what users experienced and correlate it with real user monitoring signals like Core Web Vitals, user actions, and traces, which makes it a powerful tool for investigating bugs and running root cause analysis. Session Replay is powered by Faro, Grafana's open source JavaScript instrumentation library for collecting real user monitoring data. Let's walk

## From failed check to real user impact: Pairing Synthetic Monitoring and Frontend Observability in Grafana Cloud

DevFeed: [From failed check to real user impact: Pairing Synthetic Monitoring and Frontend Observability in Grafana Cloud](<https://devfeed.tech/articles/from-failed-check-to-real-user-impact-pairing-synthetic-monitoring-and-frontend-observability-in-grafana-cloud-8586.md>)

Original publisher: [Read original article](<https://grafana.com/blog/from-failed-check-to-real-user-impact-pairing-synthetic-monitoring-and-frontend-observability-in-grafana-cloud/>)

Author: Mark Meier

Published: 2026-09-12T11:22:06.456390Z

Content type: tutorial

Language: en

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

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

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.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>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [traces](<https://devfeed.tech/tags/traces.md>), [uptime](<https://devfeed.tech/tags/uptime.md>)

### AI overview

This article explains how to combine Grafana Cloud Synthetic Monitoring with Frontend Observability to connect proactive checks with real-user impact. It describes the blind spots of synthetic-only monitoring and presents a combined workflow for faster triage, impact-aware alerts, and tests that evolve with real traffic.

### Source excerpt

Say you get a support escalation about a page in the app that won't load. But when you pull up your synthetic checks, they're all green: 100% uptime, probes are passing. Something's not adding up, but which one do you trust? If you've run Grafana Cloud Synthetic Monitoring, you've been on both sides of this. Sometimes it's the ticket: real users hit a wall on the path but your checks pass cleanly. Other times, it's the inverse: a check is failing, you're in a panic, and you start trying to reproduce things for 30 minutes--only to find it was a blip from a single region, with minimal impact to real users. Neither the green dashboard nor the red alert were lying, they just weren't answering the correct question. This ends up being the root problem. Synthetic Monitoring is exceptionally good at telling you if something broke. It can not, however, tell you who it happened to, how bad it was, or why it matters. This is not a flaw in Synthetic Monitoring; it's the boundary of what a controlled, scheduled test can know. Grafana Cloud Frontend Observability helps to close this gap. Synthetic Monitoring gives you a proactive, outside-in signal; Frontend Observability gives you the real-user, inside-out signal. Together they form a closed loop: synthetic alerts end up getting some real user context, and real user data can make your synthetic tests smart. In this post, we'll look at why a synthetic-only strategy can leave blind spots, what Frontend Observability adds, and walk through practical workflows for running them together in Grafana Cloud. Along the way, you'll learn that the payoff is concrete: faster triage, alerts that carry blast-radius context, and a check suite that evolves with real traffic instead of aging against it. Green checks don't mean happy users Synthetic Monitoring is an active signal. You script a journey or declare a target, run it on a schedule from known probe locations, and in return get clean consistent results. This precise control of variables i

[Next page](<https://devfeed.tech/topics/grafana-cloud.md?cursor=WyIyMDI2LTA5LTEyVDExOjIyOjA2LjQ1NjM5MCswMDowMCIsICJhZTc4ZjU3Yi0wY2M5LTRlZTItYTY5OS0zNjQ5MjhmNTVmZWYiXQ%3D%3D>)