Monitor GCP Cloud SQL for MySQL Metrics

The Cloud SQL for MySQL integration brings instance metrics (availability, CPU, memory, disk, connections, query throughput, InnoDB activity, and replication lag) into SigNoz, with a pre-built dashboard for the service.

Cloud SQL publishes its metrics to Cloud Monitoring. SigNoz reads them through the OpenTelemetry Collector running in your GCP project.

Choose a setup method

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 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.

Step 1: Enable the service in SigNoz

1. In SigNoz, go to Integrations > Google Cloud Platform.
2. Select GCP Cloud SQL for MySQL from the service list.
3. Toggle Metric Collection on to activate the pre-built dashboard.
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:
      # Health
      - metric_name: "cloudsql.googleapis.com/database/up"
      - metric_name: "cloudsql.googleapis.com/database/instance_state"
      - metric_name: "cloudsql.googleapis.com/database/replication/replica_lag"
      # CPU, memory & disk
      - metric_name: "cloudsql.googleapis.com/database/cpu/utilization"
      - metric_name: "cloudsql.googleapis.com/database/memory/utilization"
      - metric_name: "cloudsql.googleapis.com/database/disk/utilization"
      - metric_name: "cloudsql.googleapis.com/database/network/connections"
      # Throughput
      - metric_name: "cloudsql.googleapis.com/database/mysql/queries"
      - metric_name: "cloudsql.googleapis.com/database/mysql/dml_operations_count"
      - metric_name: "cloudsql.googleapis.com/database/mysql/threads"
      - metric_name: "cloudsql.googleapis.com/database/mysql/innodb/buffer_pool_reads_count"
      - metric_name: "cloudsql.googleapis.com/database/mysql/innodb/buffer_pool_read_requests_count"
      # Errors & contention
      - metric_name: "cloudsql.googleapis.com/database/mysql/slow_queries_count"
      - metric_name: "cloudsql.googleapis.com/database/mysql/aborted_connects_count"
      - metric_name: "cloudsql.googleapis.com/database/mysql/innodb/deadlocks_count"
      - metric_name: "cloudsql.googleapis.com/database/mysql/innodb/row_lock_waits_count"
      - metric_name: "cloudsql.googleapis.com/database/disk/read_ops_count"
      - metric_name: "cloudsql.googleapis.com/database/disk/write_ops_count"

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 InnoDB buffer pool miss ratio panel derives its value from two metrics, buffer_pool_reads_count and buffer_pool_read_requests_count. Keep both in the list or the panel stays empty.

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-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).

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 GCP Cloud SQL for MySQL Overview dashboard. Panels should start filling in.
3. To check a single metric, open Metrics Explorer and query cloudsql.googleapis.com/database/cpu/utilization.

What's collected

The GCP Cloud SQL for MySQL Overview dashboard groups its 17 panels into four sections:

• Health: Server up, Instance state, Replication lag.
• CPU, Memory & Disk: CPU utilization, Memory utilization, Disk utilization, Connections.
• Throughput: Queries, DML operations, Threads, InnoDB buffer pool miss ratio.
• Errors & Contention: Slow queries, Aborted connects, InnoDB deadlocks, InnoDB row lock waits, Disk Read IOPS, Disk Write IOPS.

Next steps

• Create alerts on instance availability, CPU or memory saturation, disk growth, connection exhaustion, slow queries, aborted connects, InnoDB deadlocks, or replication lag.
• Build custom dashboards to correlate database metrics with traces from the applications querying them.
• Monitor Cloud SQL for PostgreSQL or Memorystore for Redis if your stack also uses them.

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.