An enterprise Cloud Architecture team is establishing an end-to-end automated incident detection and self-healing remediation workflow on Google Cloud for a microservice encountering resource exhaustion. Arrange the operational steps in the correct chronological order from initial alerting setup through incident resolution.
- 1Define a Cloud Monitoring alerting policy with metric threshold criteria and configure a Pub/Sub topic as the notification channel target.
- 2Cloud Monitoring detects a metric threshold breach and publishes a structured incident alert payload to the designated Pub/Sub topic.
- 3A serverless Cloud Function triggered by the Pub/Sub topic authenticates using a least-privilege service account to parse incident details.
- 4The Cloud Function executes Google Cloud API requests to gracefully restart degraded service instances and clear stuck resource locks.
- 5Cloud Monitoring observes metric recovery below threshold conditions and automatically clears the active incident status.
Answer
The correct sequence follows the full lifecycle of automated incident detection and remediation: configuring alerting policies with Pub/Sub notification targets, publishing alert payloads upon metric breach, triggering event-driven remediation functions, executing API remediation calls to restore workload health, and auto-closing the incident in Cloud Monitoring upon metric recovery.
The proper operational order follows a logical incident lifecycle: proactive monitoring configuration, metric breach detection with event publishing via Pub/Sub, serverless event ingestion and payload parsing, execution of automated API remediation scripts, and final auto-closure of the incident state by Cloud Monitoring upon verified service recovery.
Step-by-Step Solution
Key Concept
Automated Incident Lifecycle Management and Event-Driven Remediation in Google Cloud