What's changed: Created Associate Cloud Engineer Chapter 4 (Domain 4 "Operating": operating compute/storage/networking = snapshots/images/GKE node pools-autoscaling/Cloud Run traffic splitting/object lifecycle/DB backup/subnet expansion/static IPs/Cloud DNS/Cloud NAT; monitoring and logging = Cloud Monitoring (metrics/alerts/custom metrics)/Ops Agent/Managed Service for Prometheus/Cloud Logging (log router/export)/audit logs).
4.2Monitoring and logging
Understand operational observability: metrics, alerts, and custom metrics with Cloud Monitoring; viewing/filtering logs, log buckets and log routers, and external export with Cloud Logging; deploying the Ops Agent and Managed Service for Prometheus; and audit logs and checking Google Cloud status.
Stable operations require observability—knowing "what is happening now." Google Cloud Observability centers on Cloud Monitoring (metrics) and Cloud Logging (logs).
4.2.1Cloud Monitoring
Cloud Monitoring monitors metrics like CPU, latency, and availability, and notifies via alerts when thresholds are crossed. App-specific metrics can be ingested as custom metrics. To collect detailed VM metrics and logs, deploy the Ops Agent; for Prometheus-style monitoring, use Managed Service for Prometheus. Map "monitor resource state numerically and notify = Cloud Monitoring (alerts)."
4.2.2Cloud Logging and audit logs
Cloud Logging collects and stores logs and lets you view and filter them in the console for investigation. Logs are stored in log buckets, routed by the log router, and can be exported to BigQuery, Cloud Storage, or Pub/Sub. Cloud Audit Logs record "who did what and when" for security investigation and compliance. During incidents: "detect anomalies via metrics (Monitoring) → trace causes via logs (Logging)," and "check Google Cloud status for broad outages."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.