Prepare and test your skills

Prepare and test your skills

Personalized Service Health (PSH) (opens in a new tab) events are tailored status updates about Google Cloud disruptions that affect a specific project or organization. The Service Health dashboard in the Google Cloud console is the main place to view these events, while the Service Health API, alerts, and logs deliver the same information to other tools. Each event describes its state, start and end times, impacted products and locations, and progress updates so operators can tell whether a problem comes from their own project or from Google Cloud.
The Service Health dashboard shows incidents that are relevant to the selected project, including their state and the impacted Google Cloud products and locations. Emerging and active incidents appear alongside past incidents, so the dashboard provides both current status and historical health data for troubleshooting. Events can be filtered by service, location, relevance, and status, and Organization Views aggregates the same information across every project in an organization instead of checking projects one by one.
An event annotation on a chart shows a start time and a duration, with the duration shown by a change in the chart background color. Selecting an event opens details such as scope of impact, symptoms, workarounds, mitigation steps when available, and expected resolution time. The tooltip for a Google Cloud incident identifies the following information:
Placing the pointer on a chip lists the specific affected products or locations, which helps connect the platform event to the resources the project actually uses.
Severity and operational impact in Personalized Service Health are evaluated through relevance, scope, and location rather than through a single score. The dashboard filters events by relevance, using the values RELATED, IMPACTED, and PARTIALLY_RELATED, so only events for services the project uses are shown and events marked as FALSE_POSITIVE are excluded. Checking the impacted products, impacted locations, and relevance together answers which projects are affected, which dependent products are affected, and whether specific resources in those locations are affected.
Google Cloud separates broad, severe incidents from more limited incidents by scope. A Broad Severe incident has global impact or affects a significant percentage of customer projects across multiple regions, while other confirmed incidents have limited scope such as a single location, zone, or smaller subset of projects. Broad Severe incidents are marked as Service outage and receive a public incident report after resolution, while limited-scope incidents may receive a nonpublic report shared with affected customers.
To scope an incident from the dashboard, work through the related facts in order:
Google Cloud Service Health (CSH) (opens in a new tab) is the public status page at status.cloud.google.com, formerly called Google Cloud Status Dashboard before March 24, 2022. Personalized Service Health always carries the most information for customers, and Google Cloud Service Health serves as a fallback when Personalized Service Health itself is unavailable, when sign-in through Identity and Access Management (IAM) is affected, or when a product has not yet onboarded to Personalized Service Health. Manual runbooks should direct operators to the public dashboard if they cannot access the personalized dashboard.
The two views differ in audience and detail, as shown below:
| View | Audience and access | What it shows |
|---|---|---|
| Personalized Service Health (PSH) | Signed-in view personalized to projects or an organization; available in console dashboard, Service Health API, and Cloud Logging | Emerging, active, updated, and past events relevant to those projects, with product, location, and update details |
| Google Cloud Service Health (CSH) | Public view with no login; available as dashboard and RSS feed | Broad Severe incidents affecting many projects or regions, plus status during Personalized Service Health disruption |
Automated systems can use the Service Health Status API to detect a Personalized Service Health problem and then fall back to ingesting the public CSH RSS feed for continued updates. Integration with monitoring tools (opens in a new tab) follows this same pattern of using the personalized channel first and the public channel when the personalized channel cannot be reached.
Exam tip: Personalized Service Health shows all potentially relevant events for services in use, while Google Cloud Service Health shows only Broad Severe incidents plus events during Personalized Service Health unavailability.
Personalized Service Health (PSH) (opens in a new tab) access and notifications control who can see Google Cloud health data and how teams learn about disruptions automatically. Access to the dashboard, alerts, and API all depend on Identity and Access Management (IAM), while proactive notifications also depend on Cloud Logging and Cloud Monitoring. Personalized Service Health is the primary, personalized channel for incidents relevant to specific projects or an organization.
Access to health data in Personalized Service Health is controlled by Identity and Access Management and requires sign-in to the Google Cloud console. The console dashboard is available by default once IAM grants viewing access, but programmatic access requires enabling the Service Health API for the project first. Viewing events for applications also requires specific permissions such as servicehealth.events.list, plus apphub.applications.get and apphub.applications.list when using App Hub.
The three ways to integrate have different dependencies:
| Integration point | Use case | Dependencies |
|---|---|---|
| Console dashboard | View active disruptions personalized to your projects | IAM, Google Cloud console |
| Alerts | Get proactive, personalized notifications | IAM, Cloud Logging, Cloud Monitoring |
| API | Integrate health data with another system or tool | IAM, enabled Service Health API |
Organization Views and the OrganizationEvents API extend this same IAM-controlled access from a single project to an entire organization. Instead of checking individual projects, Organization Views aggregates impacted services and projects at the organizational level. Because Personalized Service Health depends on IAM for authentication, a severe disruption that affects sign-in can block access to Personalized Service Health itself.
Proactive notifications in Personalized Service Health flow from event logs to alert notifications. Personalized Service Health writes service health events to Cloud Logging, Cloud Monitoring watches those logs with an alerting policy, and the policy sends a notification to a channel such as a mobile device, dashboard, or tool like PagerDuty. You can create an alert from the preconfigured options on the Service Health Dashboard page, including delivery to a mobile device.
A process flow showing how a Google Cloud disruption triggers a service health event that Personalized Service Health writes to Cloud Logging, where a Cloud Monitoring alerting policy filters by product, location, and relevance (Related or Impacted), then sends a notification to a channel such as a mobile device, dashboard, or PagerDuty, prompting the operator to open the Service Health dashboard for incident details.
You can set alert conditions for situations such as:
This filtering keeps notifications relevant and avoids paging on-call staff for every event. A common practice is to focus alerts on only the most critical services and locations, or to trigger only on events with relevance of Related or Impacted. Once an alert fires, you open the Service Health dashboard for your project or organization to see which projects, products, and locations are affected and to find mitigation and expected resolution time.
Exam tip: Personalized Service Health requires IAM sign-in and is personalized to your projects, while Google Cloud Service Health at status.cloud.google.com requires no login and shows broad severe incidents.
Global and Personalized Service Health are two views of Google Cloud service disruptions with different scopes. The global public dashboard shows the overall status of Google Cloud products and locations for all customers. Personalized Service Health filters that status to incidents that affect resources in active projects. Use the global view for general awareness and the personalized view to decide if an incident affects workloads.
Global and Personalized views differ in audience, scope, and actionability. The following comparison summarizes the practical difference for operations:
| View | Scope | Information provided |
|---|---|---|
| Global Service Health dashboard | All Google Cloud products and locations | General incident status visible to everyone |
| Personalized Service Health | Active project resources | Targeted incidents tied to your projects, products, and locations |
An incident can appear on the global dashboard without affecting specific projects. Personalized Service Health connects the event to the project container, location, and impacted products, so only relevant disruptions are shown. Check the global view to learn that something is happening, then check the personalized view to confirm impact to resources.
Personalized Service Health shows incident context that is tied to project resources. Each event links to an incident details view that identifies the project, location, and event, and describes what is affected and its current condition. The details focus on project scope rather than the full global incident list.
The incident view includes:
This project-scoped context lets teams move from awareness to response, because the location, product, and state fields show where to look and whether the event is still active.
Alerting in Personalized Service Health depends on relevance, alert policy configuration (opens in a new tab), and API access. The Service Health API (opens in a new tab) (servicehealth.googleapis.com) must be enabled in the project, or API calls fail with a 403 PERMISSION_DENIED and SERVICE_DISABLED error. After enabling the API, wait a few minutes for the change to propagate before retrying.
If no alert fires for a new incident, check relevance first and then check whether the alert policy is misconfigured. A policy with the wrong product, location, or condition filter can miss events that are visible in the dashboard. Example alerting policies (opens in a new tab) show how to filter by critical services, locations, and relevance values to avoid missing relevant events.
Exam tip: Personalized Service Health will not send a notification if an incident has a relevance of Unknown, even if alerting is otherwise configured.
Personalized Service Health (PSH) is the signed-in personalized view that shows emerging, active, updated, and past events relevant to specific projects or an organization with product, location, and update details, while Google Cloud Service Health (CSH) is the public view at status.cloud.google.com that requires no login and shows Broad Severe incidents affecting many projects or regions. PSH is available through the console dashboard, Service Health API, and Cloud Logging and CSH is available as a dashboard and RSS feed, and CSH serves as a fallback when PSH itself is unavailable, when sign-in through Identity and Access Management is affected, or when a product has not yet onboarded to PSH.
The Service Health dashboard shows incidents relevant to the selected project, including their state and the impacted Google Cloud products and locations, with emerging and active incidents alongside past incidents for current status and historical data. Events can be filtered by service, location, relevance, and status, and selecting an event opens details such as scope of impact, symptoms, workarounds, mitigation steps when available, and expected resolution time. Organization Views aggregates the same information across every project in an organization instead of checking projects one by one.
Access to Personalized Service Health (PSH) is controlled by Identity and Access Management (IAM) and requires sign-in to the Google Cloud console, with the console dashboard available by default once IAM grants viewing access but programmatic access requiring the Service Health API to be enabled for the project. Proactive notifications flow from PSH event logs in Cloud Logging to an alerting policy in Cloud Monitoring that sends a notification to a channel such as a mobile device, dashboard, or tool like PagerDuty, and conditions can filter for new incidents, updated incidents, or incidents for specific products, locations, or relevance values such as Related or Impacted.
An administrator is investigating potential infrastructure disruptions across their cloud deployment. While reviewing the Personalized Service Health dashboard in the Google Cloud console, they identify an active incident affecting Compute Engine. The event details display an Event State of Active (Confirmed) and a Relevance value of Partially Related.
How should the administrator interpret the Partially Related relevance status regarding the operational impact on their project?
Last updated