GCloudCLI icon
If icon
SlackIncomingWebhook icon
Schedule icon

Google Cloud SQL Database Connection and Health Sentinel

Audits Google Cloud SQL instances to detect database state degradation and connection capacity saturation.

Categories
CloudData

How it works

This workflow executes gcloud sql instances describe and queries Cloud Monitoring for database connection telemetry. Cloud SQL managed instances (PostgreSQL, MySQL, SQL Server) report operational health via state == 'RUNNABLE'. If an instance enters maintenance restart, storage auto-resize deadlock, or replication failure, the state changes to SUSPENDED, FAILED, or MAINTENANCE. Slack is alerted immediately upon any non-runnable status.

What you get

  • Continuous monitoring of Google Cloud SQL managed database operational state.
  • Prevents undetected database outages and failover delays.
  • Integrates live connection telemetry for capacity planning.

Who it's for

  • Database Administrators (DBAs) and SREs managing Google Cloud SQL production instances.
  • Platform teams running transactional applications on GCP.

Why orchestrate this with Kestra

  • Native Cloud SQL API Invocation: Direct inspection via official Google Cloud tooling.
  • Continuous Availability Verification: Run 15-minute scheduled health audits.
  • Instant Triage: Rapid escalation to on-call database response teams.

Prerequisites

  • Google Cloud SQL instance deployed with Cloud Monitoring.
  • Secrets GCP_SERVICE_ACCOUNT and SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import the blueprint.
  2. Configure project ID and instance ID.
  3. Run the workflow to inspect database status.

How to extend

  • Monitor cloudsql.googleapis.com/database/disk/utilization alongside state.
  • Automatically scale instance tier upon sustained CPU saturation.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.