GCP Integration - Monitor Google Cloud Metrics

The SigNoz GCP Integration brings metrics from your Google Cloud services into SigNoz, with pre-built dashboards for supported services. You connect a GCP account in the SigNoz UI, deploy an OpenTelemetry Collector inside your own GCP project, and point it at SigNoz.

This first release uses a manual flow: you create and own the GCP resources (a service account and an OpenTelemetry Collector). SigNoz guides you through each resource with the docs in this section.

The GCP integration is available on SigNoz Cloud and SigNoz Enterprise (Self-Hosted). Logs and traces are not part of this integration. Send traces by instrumenting your applications directly.

How it works

GCP does not PUSH telemetry to third parties, so SigNoz collects it with an OpenTelemetry Collector that runs inside your GCP project:

Metrics live in Cloud Monitoring and are pulled through the Monitoring API. The Collector's googlecloudmonitoring receiver scrapes them on an interval and exports them to SigNoz over OTLP.

The Collector must run in your environment because the Monitoring API authenticates callers as a GCP service account, not with a SigNoz ingestion key, so SigNoz cannot read your metrics directly. The Collector runs where those credentials live, which also keeps the pipeline within GCP's trust boundary.

These guides use Cloud Run for the Collector because it is the quickest managed option, but it is not required. You can run the Collector on any compute you prefer (a Compute Engine VM, GKE, an existing Kubernetes cluster, or a Cloud Run worker pool). The metrics receiver works anywhere it can authenticate to the Monitoring API.

Architecture diagram: Cloud Monitoring flows into an OpenTelemetry Collector on Cloud Run, which exports metrics to SigNoz over OTLP — *GCP integration architecture: an OpenTelemetry Collector in your project pulls metrics from Cloud Monitoring, then exports them to SigNoz*

Setup

Choose how you want to connect GCP to SigNoz:

Manual Setup

Create and own the GCP resources yourself: a service account and an OpenTelemetry Collector. Available now.

SigNoz Agent (Coming soon)

SigNoz deploys and manages the Collector for you: connect your GCP account, toggle a service on, and SigNoz provisions the metric receivers in the background.

Supported services

Once the Collector is running, enable the individual GCP services you want to monitor. Each service page lists the metrics to add to your Collector config and ships with a pre-built SigNoz dashboard.

More services are being added. Each one is configured the same way: add its metric names to the googlecloudmonitoring receiver.

Costs to expect

The manual flow runs resources in your GCP project, so the cost is billed to you, not SigNoz. Plan for:

Cloud Run (Collector): roughly ~$110/month for a Collector sized at 2 vCPU and 4 GiB running continuously. This is a comfortable default; if you ingest low volumes, you can pick a smaller configuration (for example, 1 vCPU and 1–2 GiB) to lower the cost. Size it to your throughput and scale up only if the Collector shows memory pressure or dropped data. See Cloud Run pricing.
Monitoring API (metrics): $0.01 per 1,000 read calls, with the first 1 million read calls free per billing account each month. Write calls are free. See Cloud Monitoring pricing.

Get Help

If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack. If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.