An enterprise operations team is experiencing intermittent database timeout errors across multiple microservices. The team needs to configure automated real-time incident notifications based on log entries generated by these failures. Place the operational configuration steps in the correct chronological order to establish a log-based metric and an associated Cloud Monitoring alerting policy.
- 1Specify an advanced filter query in Cloud Logging to isolate log entries containing specific database connection timeout error codes.
- 2Create a custom counter log-based metric based on the filtered query in Cloud Logging.
- 3Configure a Cloud Monitoring Alerting Policy with a metric threshold condition referencing the custom log-based metric.
- 4Attach Notification Channels and operational runbook documentation to the Alerting Policy before saving and enabling it.
Cevap
The correct operational sequence begins by defining an advanced log filter in Cloud Logging, constructing a log-based counter metric from the filtered query, creating a Cloud Monitoring Alerting Policy with threshold conditions set on that metric, and finalizing the policy by attaching notification channels and runbook documentation.
Establishing automated operational alerting based on log events follows a strict dependency path: identifying target logs via query filters, transforming log event occurrences into metric time-series data, building an alert policy with threshold evaluation rules, and attaching notification channels to complete incident dispatch.
Adım Adım Çözüm
Anahtar Kavram
End-to-end configuration sequence for log-based metrics and operational alert policies in GCP