What's changed: Created Professional Cloud Developer Chapter 6 (Domain 4 "Integration" part 2: observability = Google Cloud Observability/metrics (Monitoring)/logs (Logging)/traces (Trace)/trace-ID correlation/Gemini Cloud Assist; troubleshooting = Error Reporting aggregation, isolate metrics→traces→logs, fix/rollback).
6.1Observability (metrics, logs, traces)
Understand instrumenting code with Google Cloud Observability, collecting metrics/logs/traces, investigating with Cloud Logging, distributed tracing and correlating spans by trace ID with Cloud Trace, and AI-assisted observability.
To know what happens in production, make apps observable. With Google Cloud Observability, instrument the three pillars: metrics, logs, and traces.
6.1.1Instrumenting the three pillars
The three pillars are metrics (numeric trends; Cloud Monitoring), logs (recorded events; Cloud Logging), and traces (request paths; Cloud Trace). Instrument code to emit these and monitor via dashboards and alerts. Distinguish "numeric monitoring/alerts = metrics (Monitoring)," "recorded events/search = logs (Logging)," and "request paths = traces (Trace)."
6.1.2Investigation and correlation
Investigate failure causes by searching logs in Cloud Logging. In distributed systems, visualize the spans of services a request traversed with Cloud Trace, and correlate logs and traces by trace ID to pinpoint which service is slow or failing. Gemini Cloud Assist accelerates interpreting logs/metrics and root-cause analysis. Map "follow cross-service paths = Cloud Trace spans" and "join logs and traces = trace ID."
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.