Skip to main content

Grafana Cloud Logs and Adaptive Telemetry Enhanced

Grafana Labs announced new releases that help teams manage their telemetry in the AI era, finding the right log line in seconds and keeping only the telemetry worth paying for as AI workloads scale. 

Major query performance enhancements to Grafana Cloud Logs, built on technology from the company's Logline acquisition, are now generally available, and Adaptive Logs Archive is in public preview.

“The economics of observability only work if you keep the data worth keeping and can dial that up or down as your system’s state changes, and that’s more true than ever with the explosion in telemetry driven by AI,” said Jen Villa, Senior Director of Product, Grafana Labs. “But even the data worth keeping is still massive, so you still need to be able to find what you’re looking for in it, fast. Adaptive Telemetry handles the first, and the query performance enhancements we’ve made in Grafana Cloud Logs handle the second.”

Built on technology from Logline, which Grafana Labs acquired in April 2026, Cloud Logs now offers customers faster full-text search, at no additional cost.

This added functionality identifies logs with low frequency like request IDs and customer IDs over object storage, so an engineer paged at 1 a.m. can find the exact IDs in seconds, straight from the alert. Agents send far more queries than people do, so faster queries let agents and engineers move faster together.

Grafana Labs’ Adaptive Telemetry suite optimizes cost across metrics, logs, traces, and profiles by recommending what to aggregate or sample, so teams keep the telemetry that matters. The result is better signal at a lower cost: customers using multiple components, including Mux, TeleTracking, and Auditboard, have cut telemetry spend by 30 to 50% on average. 

New updates cover logs, metrics, and traces:

  • Adaptive Logs Archive (public preview): Adaptive Logs Archive lets teams route logs to an object storage bucket they own in an open format. They get the cost savings of not putting those logs in Grafana Cloud, but still retaining them in low-cost storage in case they’re ever needed for an investigation, audit, or compliance request.
  • Adaptive Metrics Auto-Apply (GA): Platform teams no longer have to review cardinality-reduction recommendations one by one. Auto-Apply continuously applies recommendations without a human in the loop, while existing dashboards and alerts keep working unchanged. With Cost Mode, a built-in safeguard only applies recommendations that won’t increase your total active series, so optimization never turns into a cost spike.
  • Query traces dropped by Adaptive Traces (GA): Sample aggressively without worrying about losing the one trace you need. Developers can retrieve any trace by ID from the last 24 hours, even if Adaptive Traces dropped it, so cost savings never come at the expense of an investigation.

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Grafana Cloud Logs and Adaptive Telemetry Enhanced

Grafana Labs announced new releases that help teams manage their telemetry in the AI era, finding the right log line in seconds and keeping only the telemetry worth paying for as AI workloads scale. 

Major query performance enhancements to Grafana Cloud Logs, built on technology from the company's Logline acquisition, are now generally available, and Adaptive Logs Archive is in public preview.

“The economics of observability only work if you keep the data worth keeping and can dial that up or down as your system’s state changes, and that’s more true than ever with the explosion in telemetry driven by AI,” said Jen Villa, Senior Director of Product, Grafana Labs. “But even the data worth keeping is still massive, so you still need to be able to find what you’re looking for in it, fast. Adaptive Telemetry handles the first, and the query performance enhancements we’ve made in Grafana Cloud Logs handle the second.”

Built on technology from Logline, which Grafana Labs acquired in April 2026, Cloud Logs now offers customers faster full-text search, at no additional cost.

This added functionality identifies logs with low frequency like request IDs and customer IDs over object storage, so an engineer paged at 1 a.m. can find the exact IDs in seconds, straight from the alert. Agents send far more queries than people do, so faster queries let agents and engineers move faster together.

Grafana Labs’ Adaptive Telemetry suite optimizes cost across metrics, logs, traces, and profiles by recommending what to aggregate or sample, so teams keep the telemetry that matters. The result is better signal at a lower cost: customers using multiple components, including Mux, TeleTracking, and Auditboard, have cut telemetry spend by 30 to 50% on average. 

New updates cover logs, metrics, and traces:

  • Adaptive Logs Archive (public preview): Adaptive Logs Archive lets teams route logs to an object storage bucket they own in an open format. They get the cost savings of not putting those logs in Grafana Cloud, but still retaining them in low-cost storage in case they’re ever needed for an investigation, audit, or compliance request.
  • Adaptive Metrics Auto-Apply (GA): Platform teams no longer have to review cardinality-reduction recommendations one by one. Auto-Apply continuously applies recommendations without a human in the loop, while existing dashboards and alerts keep working unchanged. With Cost Mode, a built-in safeguard only applies recommendations that won’t increase your total active series, so optimization never turns into a cost spike.
  • Query traces dropped by Adaptive Traces (GA): Sample aggressively without worrying about losing the one trace you need. Developers can retrieve any trace by ID from the last 24 hours, even if Adaptive Traces dropped it, so cost savings never come at the expense of an investigation.

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...