Chronosphere announced the general availability of its monitoring product.
This release comes after a year in beta during which Chronosphere onboarded customers from emerging startups like Tecton to later stage startups, including one of the largest delivery app companies, to well-known global brands, including a multinational financial services company.
Chronosphere delivers scalable, reliable and customizable monitoring purpose-built for companies adopting cloud-native.
Chronosphere’s product is powered by the open source metrics engine M3 that Chronosphere founders Martin Mao, CEO, and Rob Skillington, CTO, developed while at Uber. There they experienced first-hand the complexity and scale required to monitor cloud-native workloads. They solved this by scaling M3 to one of the largest production monitoring systems in the world storing tens of billions of time series and analyzing billions of data points per second in real-time.
“Everyone understands the business benefits of cloud-native architecture but not many think about the implications,” said Mao. “For monitoring, you need a solution that is not only compatible with the rest of the ecosystem but one that can also handle all of the data produced by the ephemeral and complex nature of these new environments.”
Chronosphere not only allows customers to store and retrieve the massive amounts of monitoring data produced by cloud-native environments but it also does so with an order of magnitude more cost efficient than existing solutions. Additionally, Chronosphere lets customers understand and control their spending, even as the data continues to grow. This level of visibility and control is the first of its kind in an industry notorious for unexpected and uncontrollable bills. Chronosphere customers are able to end billing overages and reduce monitoring costs by up to 10 times.
Chronosphere’s monitoring product is provided as a hosted service, eliminating the need to manage monitoring infrastructure while maintaining 100% compatibility with cloud-native standards like Prometheus, PromQL and Grafana Dashboards. Customers can retain the vendor-neutral industry standards and tooling they have grown to love without worrying about the management overhead.
Chronosphere also announced $43.4 million in Series B funding, bringing the total raised to $55 million. This round was led by previous investors Greylock, Lux Capital and venture capitalist Lee Fixel with participation from new investor General Atlantic.
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 ...