Engineering for Reliability
How to use metrics scopes in Cloud Monitoring
Twenty-three substantive episodes on SLOs, telemetry, alerting, investigation, and operations
Twenty-three 2021–2022 episodes connect user-facing reliability targets to metrics, logs, traces, and alerts. Examples show instrumentation, Prometheus collection, quota monitoring, GKE investigation, and observability cost controls.
Google Cloud Tech 9 of 23
In this collection Browse 23 summaries 9 of 23
Cloud Monitoring metric scopes let a team view measurements from several Google Cloud projects together. A scoping project hosts the shared dashboards, alerts, uptime checks, and monitoring groups; the workloads can remain in other projects 00:00–02:07(opens in a new tab).
Key Points Covered
- Keep monitoring independent of workload deletion: The presenter recommends a dedicated scoping project so that deleting a workload project does not also delete the dashboards and alerts used for the remaining projects 01:03–02:07(opens in a new tab).
- Grant access at the intended scope: In the example, an appropriate Identity and Access Management (IAM) role on the monitoring project lets a user see staging and production metrics. Access only to staging does not grant that combined view 01:03–03:12(opens in a new tab).
- Enrollment can be automated: The walkthrough uses the Cloud Monitoring API to add a monitored-project resource to a metric scope 05:18–06:21(opens in a new tab).
Full video: https://www.youtube.com/watch?v=_FKdug6B5FM(opens in a new tab)