Mobile experts Embrace expand Real User Monitoring (RUM) solution to web, bringing expertise in OpenTelemetry and performance insights across all screens.
Embrace is extending our user-focused observability platform to support websites and web apps. With our new Web RUM launch, we're giving frontend teams full visibility into how their end users experience their products – regardless of the screen they're using.
In this OpenTelemetry expert panel, we discuss the signals, tools, and approaches to catch some sweet observability waves with OTel. And which parts of OTel still leave us a bit sunburned.
Embrace is now part of the Amazon Web Services (AWS) Independent Software Vendor (ISV) Accelerate Program and is available via AWS Marketplace, making it easier for AWS customers to adopt our observability platform and get best-in-class mobile performance insights.
We're excited to release our new guide for DevOps, SRE, and mobile teams around building better SLOs. This guide will help teams design and implement SLOs that address the incredibly complex, unpredictable nature of mobile in a way that centers the end user experience.
We're excited to introduce the new Logs Experience, which contextualizes logs within the full user experience, supports larger log messages, and presents a number of analysis updates for unrivaled troubleshooting capabilities.
The past few weeks have been a testament to the keen interest in today’s trends – and future innovations – for mobile observability. The Embrace team has been busy joining the industry’s most opinionated thought leaders on podcasts for candid conversations around the role mobile plays in the rapidly evolving observability ecosystem.
We’ve rounded up our favorites from the Embrace summer podcast tour, with standout takeaways and quotes. If one thing comes across, it’s that proactively understanding how your users are experiencing your mobile applications is a challenge and an opportunity for teams today. Consumer behavior has changed so quickly…can engineering teams keep up?
Sit back and tune in – we’ve taken notes for you already.
At Embrace, we've been excited about meeting and growing the OpenTelemetry specification for some time now. We also have a ton of domain-specific knowledge about how mobile telemetry should be collected and processed. This led to a decision point while rebuilding our mobile SDKs to emit OpenTelemetry primitives: how can we quickly inform the data ingest layer about the types of telemetry we're sending, to make its life easier?
Embrace captures all the data from all the sessions of an app. Your Error Logs, successful and failing Network Requests, and screen tap locations are all recorded by the mobile app client. That’s a lot of data. Too much data to be constantly monitoring.
