An operations team needs to set up automated alerting for specific application error logs occurring in a Compute Engine environment. Order the configuration steps from first to last to establish a complete log-based alerting workflow.
- 1Define a filter query in Cloud Logging to isolate the specific application log entries indicating critical errors.
- 2Create a counter log-based metric based on the constructed log filter query.
- 3Build a Cloud Monitoring alert policy with a threshold condition monitoring the custom log-based metric.
- 4Attach a notification channel (e.g., Slack or Email) to the alert policy to send operational notifications when triggered.
Answer
The correct operational sequence begins with defining the log filter query in Cloud Logging, followed by building a custom log-based metric, configuring the Cloud Monitoring alert policy threshold on that metric, and finally attaching notification channels to deliver the alerts.
To alert on log events, you must first construct a log filter query in Cloud Logging to identify matching log lines. Second, you convert those matching logs into a time-series metric by creating a log-based metric. Third, you set up an alert policy within Cloud Monitoring that monitors the log-based metric threshold. Finally, you attach notification channels to the alert policy to notify personnel when the condition is violated.
Step-by-Step Solution
Key Concept
Configuring custom log-based metrics and operational alert policies in Google Cloud Monitoring
Estimated Time:1m 30s