Quickstart: View service health events in the Google Cloud console

This document discusses how to use the Service Health dashboard to view active and past service health events.

You can access your Google Cloud project's service health events by opening the Service Health dashboard in the Google Cloud console. Only events within the selected project scope will appear.

Before you begin

1. Enable the Service Health API for your project.
2. Set permissions to access the Service Health dashboard.

Find the Service Health dashboard in the Google Cloud console

To access the Service Health dashboard:

1. Go to the Google Cloud console.
2. Select a Google Cloud project.
3. Select the navigation menu at the top left corner of the page.
4. Go to Tools, and select Service Health.

If you see an error message that says "You do not have sufficient permissions to view this page", set permissions to access the Service Health dashboard.

Find the Service Health dashboard on a mobile device

To view Google Cloud incidents on your mobile device:

1. Install the Google Cloud mobile application from https://cloud.google.com/app.
2. Open the Google Cloud mobile application. The Dashboard tab appears.
3. Select the Operations tab.
4. Select Personalized Service Health.

View Google Cloud incidents

Note: If Personalized Service Health itself is experiencing an issue, navigate to Google Cloud Service Health for status and updates.

The Service Health dashboard lets you view active and closed Google Cloud incidents relevant to the selected Google Cloud project. A list of Google Cloud incidents related to your project appears.

The incident list fields are:

• Event State: Indicates the overall state of the event. It can be one of the following:

  • Active: Event is actively affecting Google Cloud and will continue to receive updates.
  • Closed: Event is no longer affecting any Google Cloud product, or has been merged with another event.

  The event also has a detailed state enclosed in parentheses. It can be one of the following:

  • Emerging: Google engineers are actively investigating the event to determine the impact.
  • Confirmed: The incident is confirmed as affecting at least one Google Cloud product. Ongoing status updates will be provided until it is resolved.
  • Merged: The incident was merged into a parent incident. All further updates will be published to the parent only.
  • Resolved: The incident is no longer affecting any Google Cloud product after action was taken. There will be no further updates.
  • False positive: Upon investigation, Google engineers concluded that the incident is not affecting a Google Cloud product. This state can change if the incident is reviewed again.

  • Auto-closed: The incident was automatically closed because of the following reasons:

    • The impact of the incident could not be confirmed.
    • The incident was intermittent or resolved itself.

    The incident does not have a resolution because no action or investigation happened. If it is intermittent, the incident may reopen.

• Title: Brief description of the incident.

• Relevance: Describes how an incident impacts your project. The relevance may change as the incident progresses.

  • Impacted: The incident is verified to be impacting your project. Available for some Google Cloud products only, including Compute Engine and Persistent Disk.
  • Related: The incident has a direct connection with your project and impacts a Google Cloud product in a location your project uses.
  • Partially Related: The incident is associated with a Google Cloud product your project uses, but the incident may not be impacting your project. For example, the incident may be impacting a Google Cloud product that your project uses, but in a location that your project does not use.
  • Not Impacted: The incident is not impacting your project.
  • Unknown: The impact to your project is not known at this point.
  Note: Google may determine that an earlier reported incident did not impact your project, or did not have customer impact to any projects. Personalized Service Health will inform you by setting the relevance of the incident as Not Impacted. You may also see an update published from Google Cloud Support.

• Impacted products: The Google Cloud products known to be affected by the incident. If the incident is impacting multiple Google Cloud products, you can see the list of products by doing one of the following:

  • Expand the Impacted products entry in the list.
  • Navigate to the incident.

• Impacted locations: The locations known to be affected by the incident. If the incident is impacting multiple Google Cloud locations, you can see the list of locations by doing one of the following:

  • Expand the Impacted locations entry in the list.
  • Navigate to the incident.

• Incident start time: The time Personalized Service Health detected the incident.

• Last update: The latest update from Google Cloud Support.

You can filter any field by entering a query in the filter bar or clicking a filter pill on the table.

To view the details of a single Google Cloud incident, select the title of an incident from the incident list. In the incident details page, you can navigate between tabs showing a overview of the incident and full history.

The fields in the Overview tab are:

• Event State: The overall state of the event.
• Title: A brief description of the incident.
• Event timeline: A detailed timeline of the incident so far. The timeline is not specific to your project.
• Impacted products and locations: A list of all Google Cloud products and locations known to be affected by the incident, including products and locations you may not be using.
  • Relevance: Describes how an incident impacts your project.
• Most recent update: The latest update from Google Cloud Support.
• Diagnosis: The cause of the incident.
• Workaround: Steps to mitigate the impact of the incident to your project.

The Full Incident History tab contains a complete list of updates from Google Cloud Support for the history of the incident.