Cloud Monitoring Promql Alert Incident Autoclose

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A DevOps engineer is configuring proactive alerting policies in Google Cloud Monitoring using Prometheus Query Language (PromQL) to detect performance anomalies across a microservices cluster. The engineer defines an alerting condition with an Evaluation interval set to 120 seconds (2 minutes).

During a test, a brief anomaly causes the PromQL condition to evaluate to true, opening a new incident. On subsequent evaluations, the metric normalizes and no longer meets the condition. The engineer observes that the incident does not follow the standard incident autoclose duration configured at the policy level.

How does Cloud Monitoring determine when to automatically close an incident created by this PromQL-based alerting policy?

The incident automatically closes after a duration equal to the larger of 270 seconds or twice the condition's evaluation interval following the last time the condition was met.

The incident remains open until the policy's configured Incident Autoclose Duration expires, which defaults to 7 days.

The incident remains open indefinitely until an engineer manually resolves it in the Cloud Monitoring console or via the Cloud Monitoring API.

The incident closes immediately during the subsequent evaluation cycle in which the PromQL expression evaluates to false or returns an empty vector.

Professional Cloud DevOps Engineer

Cloud Monitoring Promql Alert Incident Autoclose

Related questions