[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[],[],null,["# Personalized Service Health overview\n\nThis document provides an overview of Personalized Service Health, which lets\nyou identify Google Cloud service disruptions relevant to your projects so you\ncan manage and respond to them efficiently. These disruptions are called service\nhealth events, and are available in the Google Cloud console and a variety of\nintegration points.\n\nHow Personalized Service Health works\n-------------------------------------\n\nThe following diagram shows how Personalized Service Health makes service health\nevents available.\n\nYou can access service health events with the following:\n\n- **Service Health dashboard** : Track emerging and active Google Cloud [incidents](#incident) relevant to your projects.\n- **Service Health API**: Pull service health event information per project or organization.\n- **Alerts**: Get notified of events relevant to your projects. Alerts are based on logs in Cloud Logging.\n- **Logs**: Export logs related to Google Cloud events.\n\n### View active and past Google Cloud incidents in the Service Health dashboard\n\nThe Service Health dashboard in the Google Cloud console shows\nincidents that are relevant to your project, their state, and the impacted\nGoogle Cloud products and locations.\n\nSee the [quickstart](/service-health/docs/view-events) to learn how to access the\nService Health dashboard.\n\n### View Google Cloud incidents and receive alerts on a mobile device\n\nThe Service Health dashboard is also [available on a mobile device](/service-health/docs/view-events#service-health-dashboard-mobile).\n\nTo receive alerts on your mobile device, you can\n[configure an alerting policy](/service-health/docs/configure-alerts-cloud-logging) to send alerts\nto your mobile device.\n\n### Request service health events using the Service Health API\n\nThe Service Health API lets you get service health events that might be\nimpacting or have impacted your project, or get event details such as updates,\nstart and end times, impacted Google Cloud products and locations, and\nstate.\n\nSee the [Service Health API reference](/service-health/docs/reference) for more information.\n\n### Configure alerts or export logs through Cloud Logging\n\nPersonalized Service Health logs service health events in\n[Cloud Logging](/logging/docs/overview), and lets you\nset up alerts based on these logs. You can set up alerts for conditions such as\nwhen new incidents are reported, when existing incidents are updated, or when\nincidents for specific Google Cloud products or locations are created or\nupdated.\n\nSee the [quickstart](/service-health/docs/configure-alerts-dashboard) for setting up an alert in\nthe Service Health dashboard.\n\n### View Google Cloud incidents for your applications\n\nIf you manage Google Cloud resources using\n[App Hub](/app-hub/docs/overview),\n[Cloud Hub](/hub/docs/overview) lets you view Google Cloud\nincidents for your applications. This feature supports incidents that meet both\nof the following conditions:\n\n- Related to [products that support App Hub](/app-hub/docs/supported-resources) and Gemini Cloud Assist.\n- Have [Related relevance](/service-health/docs/overview#relevance).\n\nIf you don't have an application set up, do the following to display incidents\nin Cloud Hub:\n\n1. [Configure a folder for application management](/resource-manager/docs/manage-applications).\n2. [Set up App Hub and create an application](/app-hub/docs/set-up-app-hub).\n3. If needed, ensure that you have the following permissions:\n - `servicehealth.events.list`\n - `apphub.applications.get` on the specific application\n - `apphub.applications.list`\n4. If needed, [enable the App Hub API](https://console.cloud.google.com/marketplace/product/google/apphub.googleapis.com).\n\nConcepts\n--------\n\nPersonalized Service Health uses the following concepts to denote events affecting your\nproject, and how these events are connected to your project.\n\n### Service health event\n\nA service health **event** ([v1](/service-health/docs/reference/rest/v1/projects.locations.events#resource:-event),[v1beta](/service-health/docs/reference/rest/v1beta/projects.locations.events#resource:-event))\nis any disruptive event impacting a Google Cloud product that is\nrelevant to your projects or resources. Examples include network outages,\nconfiguration errors, and performance issues.\n\nEach event contains details about the overall impact of the event, updates from\nGoogle, and information specific to your Google Cloud project.\n\n### Incident\n\n**Incidents** are emerging and active Google Cloud service outages or\ndegradations relevant to your projects. It is a category of a service health\nevent.\n\nAn incident includes the following:\n\n- **Incident impact**: Details of the scope of the event, such as impacted Google Cloud products and locations.\n- **Updates from Google Cloud**: Periodic updates from Google Cloud support.\n- **Personalized relevance**: Incident's relevance to your Google Cloud project.\n- **Symptoms, workarounds, and ETAs**: Information to help assess impact, apply a workaround, or learn more about the root cause.\n\nAn incident may have an **incident report**, which includes the factors that\ncontributed to the incident, and the steps Google Cloud plans to take to prevent\nsimilar incidents from reoccurring. Incident reports are available for incidents\nthat meet the following conditions:\n\n- The incident has global impact or is affecting a significant percentage of customer projects across one or more regions.\n- One or more products are unavailable or severely degraded.\n\n### Event states and detailed states\n\nAn event has two fields indicating their state. The values for these fields\nchange as the event evolves.\n\n- **Event state**: Indicates the overall state of the event. It can be one of\n the following:\n\n - **Active**: Event is actively affecting Google Cloud and will continue to receive updates.\n - **Closed**: Event is no longer affecting any Google Cloud product, or has been merged with another event.\n- **Detailed state**: Provides more information on the state of the event.\n It applies to incidents only, and can be one of the following values\n depending on the event state:\n\n - **Emerging**: Google engineers are actively investigating the incident\n to determine the impact. An emerging incident will become either a\n confirmed or resolved incident once the impact assessment is complete.\n An active incident can be an emerging incident.\n\n Support for emerging incidents is available for Google Cloud\n networking products only.\n - **Confirmed**: The incident is confirmed by Google engineers and\n impacting at least one Google Cloud product. Ongoing status\n updates will be provided until it is resolved.\n\n An active incident can be a confirmed incident.\n - **Merged**: The incident was merged into a parent incident. All further\n updates will be published to the parent only.\n\n - **Resolved**: The incident is no longer affecting any Google Cloud\n product after action was taken. There will be no further updates.\n\n A closed incident is usually a resolved incident.\n - **False positive**: Upon investigation, Google engineers concluded that\n the incident is not affecting a Google Cloud product. This state can\n change if the incident is reviewed again.\n\n - **Auto-closed**: The incident was automatically closed because of\n the following reasons:\n\n - The impact of the incident could not be confirmed.\n - The incident was intermittent or resolved itself.\n\n The incident does not have a resolution because no action or\n investigation happened. If it is intermittent, the incident may reopen.\n\n### Relevance\n\nPersonalized Service Health assesses the impact of all incidents to your project. If the\nincident's impact to your project is possible or confirmed, it becomes available\nin the Service Health dashboard and API.\n\n**Relevance** describes how an incident impacts your project. The relevance may\nchange as the incident progresses.\n\nRelevance can have the following values:\n\n- **Impacted** : The incident is verified to be impacting your project. Available for [some Google Cloud products only](/service-health/docs/supported-products).\n- **Related**: The incident has a direct connection with your project and impacts a Google Cloud product in a location your project uses.\n- **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.\n- **Not Impacted**: The incident is not impacting your project.\n- **Unknown**: The impact to your project is not known at this point."]]
