Você receberá uma resposta JSON semelhante a esta:
{
"name": "projects/PROJECT_ID/locations/global/events/EVENT_ID",
"title": "We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.",
"description": "The issue with Google Cloud SQL has been resolved for all affected projects as of Tuesday, 2022-10-18 11:00 US/Pacific. We thank you for your patience while we worked on resolving the issue.",
"category": "INCIDENT",
"detailedCategory": "CONFIRMED_INCIDENT",
"state": "CLOSED",
"detailedState": "RESOLVED",
"artifacts": [
{
"artifact": "projects/PROJECT_ID/locations/global/artifacts/artifact_id",
"artifactCategory": "ARTIFACT_CATEGORY_INCIDENT_REPORT",
}
],
"eventImpacts": [
{
"product": {
"productName": "Google Cloud SQL",
"id": "hV87iK5DcEXKgWU2kDri",
},
"location": {
"locationName": "us-central1",
}
}
],
"relevance": "RELATED",
"updates": [
{
"updateTime": "2022-10-18T17:41:20.112287Z",
"title": "We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.",
"description": "We are experiencing an intermittent issue with Google Cloud SQL. Our engineering team continues to investigate the issue.",
"symptom": "None at this time.",
"workaround": "None at this time."
},
{
"updateTime": "2022-10-18T18:00:05.690761Z",
"title": "We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.",
"description": "The issue with Google Cloud SQL has been resolved for all affected projects as of Tuesday, 2022-10-18 11:00 US/Pacific.\n\nWe thank you for your patience while we worked on resolving the issue.",
"symptom": "None at this time.",
"workaround": "None at this time."
}
],
"updateTime": "2022-10-18T18:00:05.690761Z",
"startTime": "2022-10-18T17:41:20.112287Z",
"endTime": "2022-10-18T18:00:05.690761Z",
}
Se você não tiver as permissões para receber eventos, vai aparecer o seguinte erro PERMISSION_DENIED.
{
"error": {
"code": 403,
"message": "Permission 'servicehealth.events.get' denied on resource '//servicehealth.googleapis.com/projects/PROJECT_ID/locations/global/events/EVENT_ID' (or it may not exist).",
"status": "PERMISSION_DENIED",
"details": [
{
"@type": "type.googleapis.com/google.rpc.ErrorInfo",
"reason": "IAM_PERMISSION_DENIED",
"domain": "servicehealth.googleapis.com",
"metadata": {
"resource": "projects/PROJECT_ID/locations/global/events/EVENT_ID",
"permission": "servicehealth.events.get"
}
}
]
}
}
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-11 UTC."],[],[],null,["# Manage events for a project\n\nThis document explains how-tos for using the Service Health API to manage\nevents affecting a single project.\n\nBefore you begin\n----------------\n\n\n[Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n1. [Enable the Service Health API](/service-health/docs/manage-access#enable-service-health-api-single-project) for the project you want to manage events for.\n2. Set [permissions to access the Service Health API](/service-health/docs/manage-access#access-service-health-api-dashboard).\n\nReferences\n----------\n\nSee the Events API reference ([v1](/service-health/docs/reference/rest/v1/projects.locations.events), [v1beta](/service-health/docs/reference/rest/v1beta/projects.locations.events))\nfor the methods you can use and the meaning of the fields in the responses.\n\nWhen setting the product or location, use the values found at\n[Google Cloud products](/service-health/docs/supported-products-locations) and\n[locations](/service-health/docs/supported-products-locations#locations).\n\nList all active incidents for a project\n---------------------------------------\n\nSee the [quickstart](/service-health/docs/list-events#list_all_active_incidents_for_a_project).\n\nGet incident details\n--------------------\n\nYou can use the Get API to view detailed information about an event.\n\n\nBefore using any of the request data,\nmake the following replacements:\n\n- \u003cvar class=\"edit\" scope=\"API_VERSION\" translate=\"no\"\u003eAPI_VERSION\u003c/var\u003e: The API version to use. Use `v1` or `v1beta`.\n- \u003cvar class=\"edit\" scope=\"PROJECT_ID\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your Google Cloud project ID.\n- \u003cvar class=\"edit\" scope=\"EVENT_ID\" translate=\"no\"\u003eEVENT_ID\u003c/var\u003e: the ID of the event.\n\n\nHTTP method and URL:\n\n```\nGET https://servicehealth.googleapis.com/API VERSION/projects/PROJECT_ID/locations/global/events/EVENT_ID\n```\n\nTo send your request, expand one of these options:\n\n#### curl (Linux, macOS, or Cloud Shell)\n\n| **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) , or by using [Cloud Shell](/shell/docs), which automatically logs you into the `gcloud` CLI . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nExecute the following command:\n\n```\ncurl -X GET \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n \"https://servicehealth.googleapis.com/API VERSION/projects/PROJECT_ID/locations/global/events/EVENT_ID\"\n```\n\n#### PowerShell (Windows)\n\n| **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nExecute the following command:\n\n```\n$cred = gcloud auth print-access-token\n$headers = @{ \"Authorization\" = \"Bearer $cred\" }\n\nInvoke-WebRequest `\n -Method GET `\n -Headers $headers `\n -Uri \"https://servicehealth.googleapis.com/API VERSION/projects/PROJECT_ID/locations/global/events/EVENT_ID\" | Select-Object -Expand Content\n```\n\nYou should receive a JSON response similar to the following:\n\n```\n{\n \"name\": \"projects/PROJECT_ID/locations/global/events/EVENT_ID\",\n \"title\": \"We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.\",\n \"description\": \"The issue with Google Cloud SQL has been resolved for all affected projects as of Tuesday, 2022-10-18 11:00 US/Pacific. We thank you for your patience while we worked on resolving the issue.\",\n \"category\": \"INCIDENT\",\n \"detailedCategory\": \"CONFIRMED_INCIDENT\",\n \"state\": \"CLOSED\",\n \"detailedState\": \"RESOLVED\",\n \"artifacts\": [\n {\n \"artifact\": \"projects/PROJECT_ID/locations/global/artifacts/artifact_id\",\n \"artifactCategory\": \"ARTIFACT_CATEGORY_INCIDENT_REPORT\",\n }\n ],\n \"eventImpacts\": [\n {\n \"product\": {\n \"productName\": \"Google Cloud SQL\",\n \"id\": \"hV87iK5DcEXKgWU2kDri\",\n },\n \"location\": {\n \"locationName\": \"us-central1\",\n }\n }\n ],\n \"relevance\": \"RELATED\",\n \"updates\": [\n {\n \"updateTime\": \"2022-10-18T17:41:20.112287Z\",\n \"title\": \"We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.\",\n \"description\": \"We are experiencing an intermittent issue with Google Cloud SQL. Our engineering team continues to investigate the issue.\",\n \"symptom\": \"None at this time.\",\n \"workaround\": \"None at this time.\"\n },\n {\n \"updateTime\": \"2022-10-18T18:00:05.690761Z\",\n \"title\": \"We are experiencing a connectivity issue affecting Google Cloud SQL in us-east1, australia-southeast2.\",\n \"description\": \"The issue with Google Cloud SQL has been resolved for all affected projects as of Tuesday, 2022-10-18 11:00 US/Pacific.\\n\\nWe thank you for your patience while we worked on resolving the issue.\",\n \"symptom\": \"None at this time.\",\n \"workaround\": \"None at this time.\"\n }\n ],\n \"updateTime\": \"2022-10-18T18:00:05.690761Z\",\n \"startTime\": \"2022-10-18T17:41:20.112287Z\",\n \"endTime\": \"2022-10-18T18:00:05.690761Z\",\n}\n```\n\nIf you don't have the\npermissions to get events,\nyou will get the following `PERMISSION_DENIED` error. \n\n {\n \"error\": {\n \"code\": 403,\n \"message\": \"Permission 'servicehealth.events.get' denied on resource '//servicehealth.googleapis.com/projects/\u003cvar scope=\"PROJECT_ID\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/global/events/\u003cvar scope=\"EVENT_ID\" translate=\"no\"\u003eEVENT_ID\u003c/var\u003e' (or it may not exist).\",\n \"status\": \"PERMISSION_DENIED\",\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/google.rpc.ErrorInfo\",\n \"reason\": \"IAM_PERMISSION_DENIED\",\n \"domain\": \"servicehealth.googleapis.com\",\n \"metadata\": {\n \"resource\": \"projects/\u003cvar scope=\"PROJECT_ID\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/global/events/\u003cvar scope=\"EVENT_ID\" translate=\"no\"\u003eEVENT_ID\u003c/var\u003e\",\n \"permission\": \"servicehealth.events.get\"\n }\n }\n ]\n }\n }\n\nTo fix the error, set the [required permissions](/service-health/docs/manage-access#access-service-health-api-dashboard)."]]