Grafana Labs announced new features tailored for Kubernetes platform teams using Grafana Cloud.
Kubernetes Monitoring is a solution for proactive monitoring and troubleshooting within the fully managed Grafana Cloud observability platform. It provides a single pane of glass across your Kubernetes infrastructure, offering out-of-the-box visualizations of user data, cost monitoring insights, preconfigured alerts, alert rules, recording rules, and AI/ML predictions to simplify tasks that have been historically complex and time-consuming to achieve with just kubectl.
The solution’s real-time visibility, alerting, and troubleshooting capabilities for Kubernetes environments help organizations like Beeswax efficiently manage and optimize their container-based infrastructure. James Wojewoda, Lead Site Reliability Engineer at Beeswax, said, “Kubernetes Monitoring on Grafana Cloud enables our engineers to have native monitoring. No longer do they have to reach out to our SRE team. Instead, they just click a button on the Grafana Cloud integrations tab, navigate to the out-of-the-box dashboard, and see all the information — CPU usage, logs, metrics — they need to solve the problem themselves. It’s so simple, helps us spot issues fast, and saves us all a lot of custom development time.”
The latest updates include:
- Contextual root cause analysis for Kubernetes-based applications: At ObservabilityCON in September, Grafana Labs announced a suite of contextual root cause analysis workflows in Grafana Cloud. These workflows leverage AI/ML to automate root cause analysis in users’ Kubernetes environments, simplifying troubleshooting and reducing MTTR. Historically, diagnosing issues in complex Kubernetes-based applications has been a time-consuming task, requiring manual correlation of data from both application and infrastructure layers. By automatically identifying and correlating anomalies across these layers, this technology provides teams with contextualized insights, enabling faster and more accurate issue resolution.
- Availability in AWS Marketplace: Kubernetes Monitoring is now available in AWS Marketplace. Now, AWS users can easily deploy the solution with a single step in the AWS console or through the AWS Command Line Interface.
- Improved operational monitoring with Sift investigations: Kubernetes Monitoring also streamlines operational monitoring with Sift investigations by instantly identifying critical deployment issues. The platform’s intelligent alerting system automatically detects deployments with insufficient ready replicas and quickly pinpoints problematic deployments and pods requiring restart. This enhanced visibility not only reduces MTTR but also significantly improves overall system reliability.
- Enhanced historical visibility: While traditional kubectl commands offer limited historical data retention and require manual intervention, Kubernetes Monitoring in Grafana Cloud provides automatic, comprehensive historical tracking of pods, nodes, and clusters—even after deletion or recreation. This enables SREs to efficiently troubleshoot post-deployment issues, optimize resource allocation, and conduct thorough incident analyses without the complexity of maintaining additional infrastructure or orchestrating multiple tools.
- Troubleshooting enhancements: Kubernetes Monitoring has added more troubleshooting tools to help users easily find deleted objects, zoom in on a graph to narrow a time range for more analysis, and jump directly to Clusters, Nodes, and workloads directly from the homepage.
- New views: One of the most popular features within Kubernetes Monitoring, cost monitoring, now provides a 90-day view of total compute cost, average cost per Pod, and average Pod count in the Cost overview tab. In addition, Kubernetes Monitoring now allows users to view energy data for their Kubernetes infrastructure components.
In addition, Grafana Labs continues to lean into its big tent philosophy while strengthening its commitment to the open source Kubernetes community by leading the development of the Kubernetes Monitoring Helm chart—a powerful open source solution for collecting comprehensive telemetry data from Kubernetes clusters. The chart enables the collection of metrics, logs, traces, and profiles, with capabilities for local processing and flexible data routing to the backend database of your choosing. While optimized for Grafana Cloud, it integrates seamlessly with open source databases including Mimir, Loki, Tempo, Pyroscope, and more. The upcoming 2.0 release will bring many improvements including the ability to send data to multiple destinations, built-in service integrations, and a simplified configuration experience.
The Latest
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...
40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...
Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...
Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...
Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...
Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...
Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...
Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...
Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...