Ce document explique comment utiliser l'API Service Health pour gérer les événements affectant un seul projet.
Avant de commencer
Définissez les autorisations d'accès à l'API Service Health.
Références
Consultez la documentation de référence de l'API Events (v1, v1beta) pour connaître les méthodes que vous pouvez utiliser et la signification des champs dans les réponses.
Lorsque vous définissez le produit ou l'emplacement, utilisez les valeurs indiquées dans Google Cloud products (produits) et locations (emplacements).
Répertorier tous les incidents actifs d'un projet
Consultez le guide de démarrage rapide.
Obtenir les détails de l'incident
Vous pouvez utiliser l'API Get pour afficher des informations détaillées sur un événement.
Avant d'utiliser les données de requête ci-dessous, effectuez les remplacements suivants :
- API_VERSION : version de l'API à utiliser. Utilisez
v1
ouv1beta
. - PROJECT_ID: ID de votre organisation Google Cloud.
Méthode HTTP et URL :
GET https://servicehealth.googleapis.com/API VERSION/projects/PROJECT_ID/locations/global/events/event-id
Pour envoyer votre requête, développez l'une des options suivantes :
Vous devriez recevoir une réponse JSON de ce type :
{ "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", }
Si vous ne disposez pas des autorisations nécessaires pour obtenir des événements, l'erreur PERMISSION_DENIED
suivante s'affiche.
{
"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"
}
}
]
}
}
Pour résoudre l'erreur, définissez les autorisations requises.