Personalized Service Health surfaces the Google Cloud incidents that actually affect your projects, through a dashboard, an API, alerts, and exportable logs.
What is Personalized Service Health?
Personalized Service Health helps you identify Google Cloud service health events relevant to your projects so you can manage and respond to them efficiently. Details of these disruptions are available in the Google Cloud console and through a variety of integration points.
Per the documentation, Personalized Service Health is your primary channel for incident information and service health events relevant to your projects. Google also uses further channels to communicate service health.
Core Features
- Service Health dashboard: Track emerging and active Google Cloud incidents relevant to your projects or organization
- Service Health API: Retrieve event information per project or organization, including updates, start and end times, impacted products and locations, and state
- Alerts: Get notified of relevant events, based on logs in Cloud Logging
- Logs: Export logs related to Google Cloud events
- Mobile access: The dashboard is also available on a mobile device
- Dynamic product names: After renames, events reference the mapped common monikers
Typical Use Cases
Incident response
Informing the on-call team early about incidents affecting their own projects, instead of manually checking a public status dashboard.
Automated routing
Forwarding relevant events through Pub/Sub, webhooks, Slack, or PagerDuty into existing operational processes.
Analysis in your own tooling
Retrieving events through the Service Health API or exporting logs for analysis in your own systems.
Incident follow-up
Reviewing past events in the dashboard, including start and end times as well as impacted products and locations.
Benefits
- Scoped to your projects: Only incidents relevant to your projects or organization
- Several integration points: Dashboard, API, alerts, and logs instead of a single channel
- Fits existing processes: Alerts through common Cloud Monitoring channels
- Available on mobile: Dashboard access from mobile devices
Integration with innFactory
As a certified Google Cloud partner, innFactory supports you with Personalized Service Health: setting up alerts, connecting them to your incident processes, and analysing event data through the API.
Contact us for a consultation on Personalized Service Health.
Available Tiers & Options
Standard
- Incident information scoped to your projects
- Access through dashboard, API, alerts, and logs
- Dashboard also available on mobile devices
- Alerts are based on logs in Cloud Logging and must be configured
Typical Use Cases
Technical Specifications
Frequently Asked Questions
What is Personalized Service Health?
Personalized Service Health helps you identify Google Cloud service health events relevant to your projects so you can manage and respond to them efficiently. Details of these disruptions are available in the Google Cloud console and through a variety of integration points.
Through which channels do I get the information?
Per the documentation, through four channels: the Service Health dashboard for active and past incidents, the Service Health API for event information per project or organization, alerts based on logs in Cloud Logging, and export of the related logs.
How does it differ from the public Cloud Service Health dashboard?
Per the documentation, Personalized Service Health is your primary channel for incident information and service health events relevant to your projects. Google uses multiple channels to communicate service health; the incident communication documentation describes the roles of Personalized Service Health and the public Cloud Service Health dashboard.
Which notification channels are supported?
Alerts can be configured across Cloud Monitoring channels, including email, Pub/Sub, webhooks, Slack, and PagerDuty.
What happens when products are renamed?
To help viewers match event disruptions with commonly marketed terms, the API and dashboard display customer-facing monikers. When products are renamed or rebranded, events reference their mapped common monikers rather than just internal identifiers.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of Google Cloud (official documentation). This page does not represent an offer by Google Cloud.
