DevOps PeachGCP Basics · Module 08
Operations – Cloud Monitoring, Alerting, Cloud Logging and Audit Logs
Observe workloads with Cloud Monitoring metrics, dashboards, uptime checks and the Ops Agent, alert the right people, route and keep logs with the Log Router, answer “who did what” with Cloud Audit Logs, and debug latency and errors with Cloud Trace, Error Reporting and Profiler.
What you will learn
- Collect metrics with Cloud Monitoring and the Ops Agent and build dashboards and uptime checks
- Create alerting policies with useful conditions and notification channels
- Route, retain, exclude and export logs with the Log Router, log buckets and sinks
- Use Admin Activity, Data Access, System Event and Policy Denied audit logs
- Find slow requests and errors with Cloud Trace, Error Reporting and Profiler
Lessons
- Cloud Monitoring: Metrics, Dashboards, Uptime Checks and the Ops Agent
Cloud Monitoring collects metrics from Google Cloud services, the Ops Agent and your apps; metrics scopes show many projects in one place, and uptime checks test your endpoints from around the world.
- Alerting Policies and Notification Channels
An alerting policy watches a condition over time and opens an incident that notifies channels such as email, Slack, PagerDuty or Pub/Sub; good alerts are actionable, tuned and documented.
- Cloud Logging: Log Router, Buckets and Sinks
Every log entry passes through the Log Router, where sinks send it to log buckets, BigQuery, Cloud Storage or Pub/Sub; exclusions cut cost, and retention is set per bucket.
- Cloud Audit Logs: Who Did What, Where and When
Admin Activity and System Event logs are always on; Data Access logs must be enabled per service and can be large; Policy Denied logs record blocked requests; viewing them needs the right logging roles.
- Cloud Trace, Error Reporting and Profiler
Cloud Trace shows where request time goes across services, Error Reporting groups crashes and exceptions from logs, and Cloud Profiler shows which code burns CPU and memory in production.