Google Cloud SQL Integration
Managed database metrics for PostgreSQL, MySQL, and SQL Server on GCP. Monitor connection pools, replication lag, and disk I/O with AI-powered anomaly detection.
How It Works
Create a GCP Service Account
Create a service account with the Monitoring Viewer and Cloud SQL Viewer roles. This grants TigerOps read-only access to Cloud SQL instance metrics via the Cloud Monitoring API.
Enable Cloud Monitoring API
Enable the Cloud Monitoring API and Cloud SQL Admin API in your GCP project. TigerOps uses these APIs to collect database performance and health metrics.
Connect Cloud SQL Instances
Add your project credentials to TigerOps and select the Cloud SQL instances to monitor. TigerOps auto-discovers all PostgreSQL, MySQL, and SQL Server instances.
Configure Database Alerts
Set thresholds for connection pool usage, replication lag, query latency, and disk space. TigerOps fires alerts before your database reaches critical thresholds.
What You Get Out of the Box
Query Performance Insights
Track slow query counts, average execution times, and top queries by resource consumption. TigerOps integrates with Cloud SQL Query Insights to surface problematic query patterns.
Connection Pool Monitoring
Monitor active connections, maximum connection limits, and connection refused events per instance. TigerOps alerts when connection pools approach saturation and identifies connection leak patterns.
Replication Lag Tracking
Track read replica replication lag in seconds. TigerOps alerts when replication lag exceeds your configured threshold and identifies the root cause in primary instance load.
Disk I/O & Storage
Monitor read/write operations per second, disk throughput, and storage utilization. TigerOps predicts when storage will reach capacity and alerts before auto-storage increase triggers.
CPU & Memory Utilization
Track instance CPU utilization, memory usage, and temp file usage. TigerOps correlates high CPU with query load patterns and recommends instance tier upgrades when needed.
Failover & Availability
Monitor high-availability failover events, instance restart counts, and maintenance window impacts. TigerOps tracks instance uptime and correlates failover events with application error rates.
Cloud SQL Integration Setup
Connect your Cloud SQL instances to TigerOps with GCP service account credentials.
# TigerOps Cloud SQL Integration
# Required IAM roles:
# roles/monitoring.viewer
# roles/cloudsql.viewer
integrations:
gcp_cloud_sql:
project_id: "your-gcp-project-id"
credentials_file: "./tigerops-sa-key.json"
# Specific instances to monitor (empty = all instances)
instances:
- prod-postgres-primary
- prod-postgres-replica
- prod-mysql-main
scrape_interval: 60s
metrics:
- cloudsql.googleapis.com/database/cpu/utilization
- cloudsql.googleapis.com/database/memory/utilization
- cloudsql.googleapis.com/database/disk/utilization
- cloudsql.googleapis.com/database/network/connections
- cloudsql.googleapis.com/database/postgresql/replication/replica_byte_lag
alerts:
cpu_utilization_percent: 80
memory_utilization_percent: 85
disk_utilization_percent: 80
connection_utilization_percent: 90
replication_lag_seconds: 30
query_insights_slow_query_ms: 1000Common Questions
Which database engines does TigerOps support for Cloud SQL?
TigerOps supports all three Cloud SQL database engines: PostgreSQL (versions 9.6–16), MySQL (versions 5.7–8.0), and SQL Server (SQL Server 2017, 2019, and 2022). Engine-specific metrics are collected and displayed in dedicated dashboards.
Does TigerOps require direct database access or just GCP API access?
TigerOps uses the Cloud Monitoring API to collect Cloud SQL system metrics — no direct database connection is required. For deeper query-level insights, TigerOps can optionally connect to Cloud SQL Query Insights via the Cloud SQL Admin API.
Can TigerOps monitor Cloud SQL Private IP instances?
Yes. Because TigerOps collects metrics through the Cloud Monitoring API rather than a direct database connection, it supports both public and private IP Cloud SQL instances without requiring VPC peering or Cloud SQL Auth Proxy.
How does TigerOps handle Cloud SQL automated backups and maintenance?
TigerOps detects maintenance window events and backup operation start/end times from the Cloud SQL Admin API. These events are overlaid on metric charts so you can distinguish performance impacts caused by maintenance from application issues.
Can I monitor Cloud SQL replicas separately from primary instances?
Yes. TigerOps tracks each Cloud SQL instance independently, including read replicas. Replica-specific metrics like replication lag and replica bytes are displayed alongside primary instance metrics with clear labeling.
Stop Reacting to Cloud SQL Outages
Connection pool alerts, replication lag tracking, and AI-powered slow query detection for Cloud SQL. Connect in minutes.