Chronosphere has added tracing capabilities to its platform for monitoring today’s complex technology stacks at large scale.
This allows users to correlate traces with metrics, adding contextual information to alerts and dashboards in order to reduce the amount of time it takes to resolve production issues.
The new feature is based on open source and CNCF technologies including OpenTelemetry, OpenMetrics and M3, all three of which Chronosphere contributes to.
Chronosphere, founded by former Uber engineers who created M3, formally launched earlier this month. Dennis Drogseth, VP at Enterprise Management Associates (EMA), said: "Chronosphere, born out of demanding real-world requirements, is a breath of fresh air with its fast time to value and proven capabilities in helping large, enterprise IT organizations proactively address complex service delivery problems across multi-cloud and hybrid cloud environments.”
Many of today’s monitoring platforms offer both metrics and tracing capabilities and claim tight integrations between the two observability pillars. However diving into these integrations, it becomes apparent that they are two separate systems that are loosely linked via a common period of time and a common set of attributes and labels. While this does help narrow down the search space, manual intervention is often required to link and make sense of the two types of monitoring data.
The problem with manual intervention is that each minute the issue remains unresolved, the business is negatively impacted and due to this, engineers are often under immense pressure to find the cause of issues quickly. An ideal solution would present all the context of the issue upfront, reducing the time it takes to identify and mitigate issues - and that is what Chronosphere’s monitoring platform offers.
Chronosphere’s solution to this problem is to deeply link the traces and metrics from the moment they are emitted. The trace identifiers are stored right next to the metric values in Chronosphere’s metrics storage system M3. When a user receives an alert or views their dashboard, the very traces that constituted those metric values are displayed instantly. This saves valuable minutes during an outage and helps users identify and mitigate issues much faster.
“The best part of our solution is that we can achieve this deep linking in a cost-efficient way,” said Rob Skillington, co-founder and CTO of Chronosphere. “This would be an easy problem to solve if you simply stored every trace, but in most cases, that’s way too expensive to do at any real level of scale.”
Chronosphere achieves cost efficiency by leveraging their existing metrics aggregation tier to selectively store unique traces. This allows users to both find that needle in a haystack - the one in a thousand error or slow request - while using a fraction of the storage.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...