Monitor GCP Cloud SQL for PostgreSQL Metrics and Logs

One-Click Integration

SigNoz deploys and manages the Collector for you. You turn the service on in SigNoz, and the SigNoz agent sets up metrics and logs collection in the background. Collects metrics and logs.

Prerequisites

• Your GCP project is connected with One-Click Integration.
• Your Cloud SQL for PostgreSQL instances run in that same project. The agent monitors only the project it's deployed in.

Step 1: Turn on the service in SigNoz

1. In SigNoz, go to Integrations > Google Cloud Platform.
2. Select GCP Cloud SQL for PostgreSQL from the service list.
3. Turn on Metric Collection, Log Collection, or both.
4. Click Save.

The agent picks up the change within about 30 seconds and updates the Collector and the log sink for you. There's no Collector config to edit.

Step 2: Turn on the optional data in GCP

Most data starts flowing with no extra work. Two kinds of data need a setting on the GCP side first:

• Query execution time panels need Query Insights turned on for the instance. It's off by default and has no extra charge.
• pgAudit logs, which record the SQL statements run on your database, need pgAudit set up on the instance and Data Access audit logs turned on for the project. See Audit a Cloud SQL instance with pgAudit.

Skip this step if you don't need these.

Validate

1. Wait about 10 minutes for the first metrics to arrive.

2. In SigNoz, go to Dashboards and open GCP Cloud SQL for PostgreSQL Overview. Panels should start filling in.

3. If you turned on Log Collection, open Logs in SigNoz and start with this filter to find your project's logs:

   Copy

   gcp.project = '<deployment-project-id>' AND gcp.resource_type = 'cloudsql_database'

   New PostgreSQL log lines from your instances appear within a few minutes.

   Verify these values:

   • <deployment-project-id>: the GCP project you connected with One-Click Integration.

Manual Setup

You run the OpenTelemetry Collector in your own GCP project and add Cloud SQL metrics to its configuration. You control which metrics are pulled and how often. Collects metrics, and logs if you set up the log pipeline.

Complete the GCP integration setup once, then follow the steps below for each Cloud SQL instance you want to monitor.

Prerequisites

Before configuring this service, complete the shared GCP integration setup:

• Your GCP account is connected in SigNoz, and the project running your Cloud SQL instances is in Projects to Monitor.
• The OpenTelemetry Collector is deployed and running.
• The signoz-integration-collector service account has roles/monitoring.viewer on the project that hosts the instances. See Create a service account.
• The Cloud Monitoring API is enabled in that project.
• For logs only: the Cloud Logging API is enabled in that project, and you have finished steps 1 to 5 of Collect logs.

Step 1: Enable the service in SigNoz

1. In SigNoz, go to Integrations > Google Cloud Platform.
2. Select GCP Cloud SQL for PostgreSQL from the service list.
3. Toggle Metric Collection on to activate the pre-built dashboard. Toggle Log Collection if you also want to send logs.
4. Open the Data Collected tab and note the metrics listed there. These are the metrics the dashboard's panels query.

Step 2: Add the metrics to your Collector config

Open the otel-collector-config.yaml you created in Deploy the Collector and add the Cloud SQL metric names to the metrics_list of the googlecloudmonitoring receiver for the project your instances run in. Only the metrics_list shown below changes; leave the rest of the file as is:

receivers:
  googlecloudmonitoring:
    project_id: "<monitored-project-id>"
    collection_interval: 300s   # 5 minutes; minimum is 60s
    metrics_list:
      # Availability
      - metric_name: "cloudsql.googleapis.com/database/up"
      # Compute
      - metric_name: "cloudsql.googleapis.com/database/cpu/utilization"
      - metric_name: "cloudsql.googleapis.com/database/memory/utilization"
      - metric_name: "cloudsql.googleapis.com/database/memory/usage"
      # Storage
      - metric_name: "cloudsql.googleapis.com/database/disk/bytes_used"
      # PostgreSQL engine
      - metric_name: "cloudsql.googleapis.com/database/postgresql/num_backends"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/num_backends_by_state"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/transaction_count"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/deadlock_count"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/vacuum/oldest_transaction_age"
      # Query insights
      - metric_name: "cloudsql.googleapis.com/database/postgresql/insights/aggregate/execution_time"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/insights/aggregate/io_time"
      - metric_name: "cloudsql.googleapis.com/database/postgresql/insights/perquery/execution_time"
      # Replication
      - metric_name: "cloudsql.googleapis.com/database/postgresql/replication/replica_byte_lag"

Verify these values:

• <monitored-project-id>: The GCP project that hosts your Cloud SQL instances. It must be one of the entries in your Projects to Monitor list.

The three insights/ metrics need Query Insights enabled on the instance (off by default, no extra charge) or their panels stay empty; drop them from the list if you don't need query timing.

The receiver polls every metric in the list once per collection_interval, and the Monitoring API bills per read call, so keep the list to the metrics your dashboards and alerts actually use. See Cost and tuning.

Step 3: Apply the configuration

The Collector loads its config from the signoz-integration-collector-config secret, so a config change needs a new secret version and a redeploy:

1. Save your updated otel-collector-config.yaml.
2. Add a new secret version (step 2 of Deploy the Collector).
3. Redeploy the Cloud Run service (step 3).

Step 4: Send logs (optional)

To also send PostgreSQL logs to SigNoz, follow Collect logs to set up the Pub/Sub topic, the push subscription, and the logs receiver. In step 6, Create a log sink, use this filter:

resource.type="cloudsql_database" AND (
  logName:"/logs/cloudsql.googleapis.com%2Fpostgres"
  OR (log_id("cloudaudit.googleapis.com/data_access")
    AND protoPayload.request.@type="type.googleapis.com/google.cloud.sql.audit.v1.PgAuditEntry")
)

See Logs under What's collected for what this filter picks up and which logs need a setting in GCP first.

Validate

1. Wait one or two collection intervals (up to about 5 minutes with the default 300s).
2. In SigNoz, go to Dashboards and open the Cloud SQL for PostgreSQL dashboard. Panels should start filling in.
3. To check a single metric, open Metrics Explorer and query cloudsql.googleapis.com/database/cpu/utilization.
4. For logs, open Logs and filter on gcp.resource_type = 'cloudsql_database'.