Grafana Labs announced the general availability of Adaptive Profiles in Grafana Cloud, completing the Adaptive Telemetry suite to span all four telemetry signals: metrics, logs, traces, and profiles.
With Adaptive Profiles now GA, every layer of an organization's observability stack can automatically identify and retain high-value data while filtering out what doesn't matter, without manual tuning or engineering toil.
Grafana Labs built the Adaptive Telemetry suite to continuously analyze how telemetry is actually used and surfacing precise recommendations for what to keep, aggregate, or drop.
"The fundamental problem with observability economics today is that cost scales with ingestion, not insight," said Steven Dungan, Staff Product Manager at Grafana Labs. "Adaptive Telemetry inverts that model. Every signal: metrics, logs, traces, and profiles, now has an intelligent layer that learns how data is used in practice, and then optimizes automatically. With Adaptive Profiles reaching GA, we've closed the loop on the full stack. Teams get more signal, less noise, and lower bills and they don't have to sacrifice one for another."
Adaptive Profiles dynamically adjusts the detail and frequency of data collection based on workload behavior. During normal operations, it collects at a cost-effective baseline. When anomalies or performance issues arise, it automatically increases resolution to ensure engineers have the data they need to investigate.
For engineering teams that have struggled to justify fleet-wide profiling, Adaptive Profiles makes the economics work, delivering richer performance data where it matters, without requiring a fixed high-cost collection rate across every service.
Across the full Adaptive Telemetry suite, organizations using multiple components see 30–50% reductions in total telemetry costs on average.
The Latest
Performance bottlenecks aren't uncommon when it comes to rolling out new technology, regardless of how capable or game-changing that technology might be. Every generation of new tech has encountered roadblocks that had to be overcome before it was truly able to shine. Virtualization forced organizations to rethink resource allocation, cloud transformation had us shift our focus toward scalability and elasticity, and microservices introduced entirely new challenges around observability and distributed systems. There's something different about AI, however ...
Consider a single order represented across order-management, execution, and settlement systems. Each database, message broker, and application may be online and processing its own records correctly. Yet the workflow has failed if related events arrive on different clocks, rely on inconsistent state, or cannot be reconciled before an operational decision must be made ...
AI now exists in almost every IT workflow. In a recent survey of more than 800 IT service professionals, all respondents indicated the use of AI in some form within their organization. But there's a growing paradox: if dashboards are clearing faster and alerts are resolved at unprecedented speed, why aren't IT service desks reporting lighter workloads? The research found that 71% of IT teams said their actual workload has remained flat or increased since adopting AI. This reality appears to contradict what we’ve been told about AI ...
Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...