Integration · Clouds
Google Cloud
GCE / GKE / Cloud Run via workload identity.
What gets collected
A service account with monitoring.viewer plus GKE workload identity for in-cluster. A Cloud Run sidecar covers the function level.
Requirements
- ✓IAM role: roles/monitoring.viewer
- ✓GKE workload identity
- ✓gcloud CLI (optional)
- ✓Cloud Run sidecar for function level
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
gce.cpugce.disk.iogke.pod.cpucloudrun.request.countcloudrun.latencymonitoring.googleapis.com/*Setup steps
- 1Create an SA with monitoring.viewer
- 2workload-identity binding for GKE
- 3Cloud Run sidecar definition
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Google Cloud
Frequently asked questions
- What does Unimoni collect from Google Cloud?
- GCE / GKE / Cloud Run via workload identity. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Google Cloud and everything else in one place.
- How long does it take to connect Google Cloud?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Google Cloud integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Google Cloud monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.