How it works
What you get
Authentication options
Service account JSON key or workload identity (same as Cloud Monitoring)
Documentation
View the full documentation. Learning path coming soon!
Products
Grafana Cloud
Monitor, analyze, and act faster with AI-powered observability.
LGTM+ Stack
Key Capabilities
Observability Solutions
Open Source
Community resources
Dashboard templates
Try out and share prebuilt visualizations
Prometheus exporters
Get your metrics into Prometheus quickly
end-to-end solutions
Opinionated solutions that help you get there easier and faster
monitor infrastructure
Out-of-the-box KPIs, dashboards, and alerts for observability
visualize any data
Instantly connect all your data sources to Grafana
Learn
Community and events
Resources
Help build the future of open source observability software Open positions
Check out the open source projects we support Downloads
Grafana Cloud
Monitor, analyze, and act faster with AI-powered observability.
Observability Solutions
The actually useful free plan
10k series Prometheus metrics
50GB logs, 50GB traces, 50GB profiles
500VUh k6 testing
20+ Enterprise data source plugins
100+ pre-built solutions
3 active AI users
end-to-end solutions
Opinionated solutions that help you get there easier and faster
visualize any data
Instantly connect all your data sources to Grafana
| Capabilities | Limitations |
|---|---|
| All GCP service logs | Cloud Logging query syntax |
| Visual query builder | API latency |
| Filter by resource, severity | Separate from metrics data source |
| Template variables | Per-project auth typically |
| Log context and details | Alert evaluation calls API. |
Service account JSON key or workload identity (same as Cloud Monitoring)
View the full documentation. Learning path coming soon!
For GCP logs, there’s a separate data source, Google Cloud Logging. This connects directly to Cloud Logging, letting you query logs from all your GCP services without storing them in Loki.
Authentication works the same as Cloud Monitoring, service account JSON key or workload identity if you’re running in GKE.
You write queries using Cloud Logging’s query language, which is similar to what you’d use in the GCP console. Filter by resource type, severity, timestamp, or any log field. The visual query builder helps if you’re not familiar with the syntax.
One thing to note: unlike AWS and Azure where one plugin handles both metrics and logs, GCP requires two separate data sources. You’ll configure Cloud Monitoring for metrics and Cloud Logging for logs.
Same authentication can work for both. Just grant your service account the appropriate roles.