Chronosphere quickly rose to the top of the list, with several capabilities hitting the company’s requirements head-on:
High availability and reliability. The Chronosphere observability platform was built from the ground-up for cloud-native scale and complexity, which means greater reliability. Chronosphere is 5X more reliable than alternative SaaS monitoring solutions and has never missed a customer SLA – a fact that was vitally important to the company given their previous challenges with availability.
Fast remediation. The faster the engineering teams know there is a problem, the faster they can start to remediate it. With Chronosphere, the company was able to reduce their MTTD issues by 4x, from 2 minutes to 30 seconds. Once the engineers are alerted, they can also load dashboards and reports much faster – dashboards that previously took 15 minutes to load, now load in seconds. On top of that, Chronosphere reduced “time to glass” – which describes the time from when a data point is generated to when it is visible in dashboards and reports – from 45 seconds to 5 seconds.
Compatible with open-source standards: Unlike other SaaS monitoring offerings, Chronosphere is open-source compliant, supporting all major open source metrics ingest protocols, dashboards, and query languages. Because Chronosphere is built on the open source M3 metrics engine, the company wouldn’t need to rely on the black box magic of monitoring a vendor’s proprietary data format, it avoided vendor lock-in, and it was able to leverage existing Prometheus investments.
Cloud-native observability expertise: Chronopshere’s co-founders Martin Mao (CEO) and Rob Skillington (CTO) previously ran the observability team at Uber where they experienced first-hand the challenges of running large-scale observability for cloud-native environments.
Ability to keep up with the business: With Chronosphere, the company found an observability partner who could keep up with their rapidly scaling business. With Chronosphere, the company is able to unlock new insights that were previously unavailable due to longer retention periods and faster load times. “After seven days, data isn’t usable. The fact that we now see data retention in excess of two years with Chronosphere is huge for us.”