You are supporting a business-critical application in production deployed on Cloud Run. The application is reporting HTTP 500 errors that are affecting the usability of the application. You want to be

Question

Options

• ACreate a Cloud Function that consumes the Cloud Monitoring API. Use Cloud Scheduler to trigger
• BNavigate to the Cloud Run page in the Google Cloud console, and select the service from the
• CCreate an alerting policy in Cloud Monitoring that alerts you if the number of errors is above the
• DCreate a Cloud Function that consumes the Cloud Monitoring API. Use Cloud Composer to

• A
  6% (3)
• B
  16% (8)
• C
  74% (37)
• D
  4% (2)

Explanation

Cloud Monitoring natively supports ratio-based alerting policies, which can compare the count of HTTP 500 errors against the total request count within a rolling time window and alert when the ratio exceeds a defined threshold (15% in this case). This is the built-in, purpose-designed solution requiring no additional code. Option A (Cloud Function + Cloud Scheduler) is an overly complex polling architecture that introduces latency and additional maintenance burden. Option B (Cloud Run page in console) provides visibility but does not send alerts. Option D (Cloud Function + Cloud Composer) adds an orchestration layer (Cloud Composer is Apache Airflow) that is completely unnecessary for a monitoring alert use case.

No community discussion yet for this question.