With Chronosphere and Personalized Service Health, you gain visibility into disruptive events that affect Google Cloud products and services. Read on to learn more.
On: Apr 9, 2024
Scott is a Senior Product Marketing Manager at Chronosphere. Previously, Scott was in product marketing at VMware (via the Pivotal acquisition) where he worked on the Tanzu Observability (Wavefront) team and partner go-to-market efforts for VMware’s Tanzu portfolio with AWS and Microsoft Azure. Before VMware, Scott spent three years in product marketing at Dynatrace. In his free time, you’ll find Scott at his local CrossFit “box”, doing home improvement projects, and spending time with his family.
Google Next ’24 is upon us and we have a few things we’d like to share with you. Since announcing our strategic partnership a year ago, we’ve made great progress, both go-to-market and engineering-wise. Our latest achievement is an integration between Chronosphere and Google Cloud Personalized Service Health. Keep reading to learn more!
Personalized Service Health allows you to “Gain visibility into disruptive events impacting Google Cloud products and services relevant to your projects.” In other words, it is your unique status page that shows you only issues related to services you actually use in Google Cloud. It supports 50+ Google Cloud products and services.
When on-call engineers respond to an issue, they need to understand what changed, where it occurred, and when it happened. These insights are critical to investigating and remediating issues when they arise. Chronosphere’s Change Events solution allows customers to centralize their change event data and use it to understand their system’s state better and debug issues faster. Now, Google Cloud customers can ingest events impacting Google Cloud products and services relevant to their projects into Chronosphere.
Personalized Service Health matched with Chronosphere’s Change Event Tracking is like peanut butter and jelly — much better together.
Why?
Seventy-seven percent of IT incidents are caused by a change, whether it be a system change, workload change, or even a change in the observability platform. Moreover, 66% of MTTR is spent identifying the change causing the problem.
In the era of cloud native technologies, the rate of change is staggering. Multiple independent service teams are pushing new code multiple times daily, configurations are constantly being tweaked, and infrastructure scales up and down within minutes.
Each of these changes is an opportunity to introduce an issue that can cascade through the system and cause degradation or failure.
Chronosphere Change Event Tracking consolidates all change events from various integrated sources (Ex. LaunchDarkly, Buildkite, and now Google Cloud Personalized Service Health) to quickly detect patterns and discern correlations across your telemetry data.
In the dashboard below, a user can quickly toggle on Google Cloud health events and overlay them on the charts to see if there is a correlation between a service health event and a change in performance. This information enables engineers to respond to issues quickly, reducing developer toil and improving their situational awareness during an incident.
“We saw immediate value in Chronosphere’s new Google Cloud Personalized Service Health integration. Having highly relevant incidents impacting the Google products we rely on overlayed in our most critical dashboards saves a lot of time. It’s great to see Chronosphere and Google Cloud working together so closely!”
Users can access Google Cloud metrics from within Chronosphere, and customers can get started quickly with our new out-of-the-box dashboards.
Currently available dashboards include:
You can also hear what our innovative customers are speaking about, observability-related or not:
Curious to learn more about Chronosphere observability?