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
IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...