Honeycomb.io announced an extended partnership with Embrace, the user-focused observability platform.
Together, the two companies are extending the rigorous, data-driven practice that Honeycomb pioneered for foundational observability to mobile and web, giving engineering, site reliability, and platform teams a complete, correlated picture of system health. The strategic partnership makes understanding performance and reliability for every user and every screen part of the observability practice, bringing new depth and standardization to how teams measure end user impact.
Backend teams have had strong tooling for server health, latency, and distributed tracing for years, but no real window into what users experience on devices and browsers. Frontend and mobile developers, meanwhile, have been underserved by traditional observability tooling that cannot provide the depth and breadth of insights required, forcing them to seek disparate tools just to identify and resolve user-impacting issues. Organizations end up with no shared data, blind spots on root causes, and a disconnect between teams that should be collaborating to improve performance and deliver better user experiences and business outcomes.
Embrace was built on OpenTelemetry, approaching frontend performance the same way Honeycomb approaches foundational observability: with high-cardinality, context-rich data that ties technical signals directly to user impact. This shared foundation means performance data from mobile apps and web browsers can flow into, be queried with, and be understood by every engineering team across the stack, with no proprietary schema standing in the way.
This technical integration brings frontend session data, crash signals, network insights, Core Web Vitals, and real user context from mobile and web surfaced inside the Honeycomb platform. Key customers leveraging both products have been asking for exactly this kind of integration.
“We’ve always believed observability is a practice, not a product category,” said Matt Nelson, Chief Revenue Officer at Honeycomb. “Embrace has applied that same rigorous, data-driven approach to the layer where users experience software. Building on OpenTelemetry means the data speaks the same language and that’s what makes this a real integration, not a dashboard mashup. SRE and platform teams can finally see the whole system, not just the parts they already owned. And their mobile and web counterparts can address issues with the same data, in great detail.”
What This Means for Engineering Teams
With this partnership, engineering teams that use both Honeycomb and Embrace benefit from:
- End user visibility, across web and mobile: Real user data from Embrace, with aggregated insights from session timelines, crash signals, network insights, and user journey context are surfaced inside Honeycomb, giving SRE, reliability, and platform engineering teams a better understanding of what’s happening on the device and in production systems.
- Expanded RUM capabilities, purpose-built for frontend engineering teams: Organizations that rely on Honeycomb for backend and infrastructure observability can now extend that same practice to their web and mobile practitioners, giving those teams the most powerful RUM tooling by Embrace, fully connected to the systems and data their reliability colleagues use.
- Native data, not a bolt-on: Both platforms are built on OpenTelemetry, which means signals and telemetry arrive in Honeycomb as standard, enriched, composable data, not a proprietary feed that requires translation. The context that makes observability useful stays intact.
- Performance tied to user impact: Embrace’s approach ties technical performance signals directly to end user experience, surfacing how frontend degradation translates to real business impact. Now, that data lives alongside telemetry in Honeycomb.
“Performance and reliability are two sides of the same coin,” said Andrew Tunall, President and Chief Product Officer at Embrace. “We built Embrace on OpenTelemetry because we believe the future of understanding complex systems is open, composable, and context-rich. This partnership is a natural extension of that belief: when the data is standard and the philosophy is shared, the integration is real. At the end of the day, users don’t care whether the root cause of an issue is service behavior, a bug, or a rendering problem, they just want your product to work.”
Embrace is available in the AWS Marketplace alongside Honeycomb, giving joint customers flexibility in how they acquire and deploy both products.
The Latest
Part 4 outlines the challenges enterprise face when adopting AI observability. The main challenge is that AI complexity compounds at every stage of maturity. LLM-based applications introduce new behavior, dependencies, and quality considerations, while Agentic AI adds further failure modes as systems make decisions and take actions ...
Part 3 reports on the current state of AI observability. Most experts agree: enterprises are moving faster with AI than they are with the operational discipline needed to run it safely ...
When discussing AI Observability, one of the first questions that arises: Is this just an extension of traditional observability or is this a whole new type of tool? Part 2 compares traditional observability with AI observability ...
In this extensive 14-part series that will post over the next three weeks, experts across observability and AI will provide insight and opinions on the need for AI Observability, the challenges, the benefits, the current state, and predictions for the future ...
Amid rising complexity, organizations are moving quickly toward agent-driven operations: AgenticOps, according to The Impact of Agentic AI on Network Operations, a new report from Cisco ...
AI, automation, and enterprise software give organizations an extraordinary amount of leverage. Work that once required hours can happen in minutes. Information buried across systems can be analyzed almost instantly. Complex workflows can be coordinated across teams with far less manual intervention. That leverage creates a temptation to start with the technology ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...
For more than a decade, the default infrastructure play has been simple. Move more workloads to the cloud, retire on-premises gear and treat the data center as a cost to shrink. That logic held while public cloud offered near-limitless capacity at predictable prices, and AI demand is now testing both halves of that assumption ...
Most enterprise IT leaders can tell you exactly how many applications are running across their organization. They can surface a dashboard showing telecom spend by region, pull a report on SaaS license utilization, or call up a real-time view of mobile device inventory. The data is there, and IT leaders have largely delivered on the promise of visibility. Yet, in most organizations, that visibility has not translated into business value ...
Government agencies are largely misjudging their level of AI governance as the technology permeates their organization, according to Racing to Deploy: How Public Sector AI Adoption is Moving Faster Than the Foundations Needed to Support It, a new report from SolarWinds ...