Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

Microsoft Azure SQL Database DTU and CPU Utilization Saturation Sentinel

Monitors Azure SQL Database for DTU and CPU percentage saturation to prevent query execution timeouts and deadlocks.

Categories
CloudData

How it works

This workflow monitors Database Throughput Unit (DTU) and compute saturation on Microsoft Azure SQL Databases using the Azure CLI container. In the DTU purchasing model, DTUs represent a blended measure of CPU, memory, data I/O, and transaction log I/O. When DTU utilization approaches 100%, incoming database queries experience severe execution stalls, worker thread contention, and connection pool timeouts. The flow queries Azure Monitor, calculates maximum DTU consumption, and triggers Slack alerts when critical thresholds are breached.

What you get

  • Proactive visibility into database compute bottlenecks before application latency escalates.
  • Prevents query execution timeouts, locking escalations, and worker thread exhaustion.
  • Quantitative telemetry regarding database workload pressure.

Who it's for

  • Database Administrators and Data Platform Engineers managing Azure SQL infrastructure.
  • Backend Engineering leads responsible for critical transactional database performance.

Why orchestrate this with Kestra

  • Cross-Cloud Health Monitoring: Standardize database monitoring workflows across Azure SQL, AWS RDS, and Google Cloud SQL.
  • Flexible Threshold Control: Easily customize alert thresholds per environment via flow inputs.
  • Secure Service Principal Integration: Zero hardcoded secrets using Kestra secret store.

Prerequisites

  • Azure Service Principal with Monitoring Reader role on the target SQL database.
  • Secrets AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, and SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import the blueprint.
  2. Configure subscription ID, resource group, server name, and database name.
  3. Run the flow to evaluate current DTU consumption.

How to extend

  • Trigger an automatic database tier scale-up via Azure CLI when sustained saturation occurs.
  • Execute a diagnostic query against sys.dm_exec_query_stats to identify the most resource-intensive SQL queries.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.