Honeycomb released Honeycomb for Kubernetes. This new capability enables platform engineers running Kubernetes and the developers building on it to correlate granular application issues in production code with their infrastructure layer.
Honeycomb for Kubernetes is available now to all Honeycomb users.
According to CNCF's 2022 Annual Survey, 64 percent of end users (engineers) have implemented Kubernetes in production today, and 25 percent are currently evaluating the solution. Kubernetes is furthering its momentum as the preferred environment for managing containerized applications, as it's easier to get feature changes provisioned and enables developers to build and release faster. However, while infrastructure dashboards within application performance monitoring (APM) suites are effective for platform engineers monitoring Kubernetes, they lack detailed application context relevant to developers diagnosing and resolving software issues. This correlation gap between Kubernetes application and infrastructure layers leads to increased operational backlog, strained resources, and decreased productivity.
"It's becoming clear that today's monitoring tools frequently underserve developers, and worse, they create unnecessary tension between devs and platform engineers," said Charity Majors, Co-founder and CTO of Honeycomb. "This blind spot serves as yet another glaring signal that observability platforms are better equipped than APM tools to provide comprehensive, granular context into how code behavior impacts application performance."
Honeycomb's new Kubernetes-aware observability features fill the visibility gaps in these complex systems, helping teams rule out application vs. infrastructure issues and address the potential bottlenecks between platform engineers and application developers. This equips teams with the confidence to release more often, keep migrations seamless, foster developer self-sufficiency, and elevate overall productivity.
For the team at Birdie Care, Sr. DevOps Engineer Harry Morgan says that Honeycomb's "out-of-the-box templates for metric analysis and correlation really help put together a more holistic picture of our environments, simplifying our workflow and eliminating the need to compare across observability platforms. At Birdie, it's important we can ask critical questions of our whole system, and with the improvements to their Kubernetes offering, Honeycomb is delivering a great addition to our toolkit in doing this."
Designed to enable seamless insight into applications in relation to the infrastructure they run on, Honeycomb for Kubernetes allows developers to correlate application requests with specific Kubernetes pods, nodes, or cluster configurations. It makes it easy to integrate data from Kubernetes using new instrumentation options for Kubernetes events, metrics, and trace attributes. These include OpenTelemetry as well as a low-code, language-agnostic agent for comprehensive coverage. In the Honeycomb UI, new correlation features make it easy to tie this Kubernetes context to any incident's events and reveal patterns. Honeycomb's approach to observability offers numerous advantages:
- Observability Efficiency: As teams adopt the complexity inherent in Kubernetes, Honeycomb helps observe their systems efficiently. Designed to scale painlessly with exponential telemetry from pods to nodes, Honeycomb includes unlimited custom attribute tags per event at no extra cost. This solves the budget/readiness tradeoff forced by per-host/metric billing.
- Human-Driven, AI-assisted Investigation: Because dashboards are limited to passively visualizing known cluster data, Honeycomb also offers developers a query-driven approach to surface unknown patterns, pinpointing what's wrong and how Kubernetes is involved. To help users navigate unfamiliar services, Honeycomb's Query Assistant uses generative AI to process natural English questions into relevant queries and produce immediate visual feedback on application performance.
- Kubernetes Context in OpenTelemetry: Honeycomb supports OpenTelemetry Kubernetes standards and simplifies instrumenting cluster context into application traces, enhancing the experience for teams adopting open-source instrumentation. By implementing Honeycomb and OpenTelemetry, platform teams also see less data and tool fragmentation. Various options are available to enable users on any language, node, or cluster.
As modern developer teams migrate towards distributed architecture, Honeycomb addresses that complexity with scalable and user-driven observability. The company's new solution for Kubernetes is the most recent example paving the way for a more open, efficient, and productive development ecosystem.
Honeycomb for Kubernetes works on platforms like Amazon EKS, Azure Kubernetes Service, or Google Kubernetes Engine as well as bare-metal Kubernetes distributions and Red Hat OpenShift.
The Latest
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 ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...