Telemetry
For teams connecting application failures and latency to database behavior

Database Reliability Monitoring with SQL

Track safe query fingerprints, pool pressure, transaction rollbacks, lock contention, replication lag, and migration outcomes without collecting raw SQL parameters.

Reviewed by the Telemetry product team on . Event contract, recommended analysis, and privacy boundaries. Editorial ownership

Why this works
  • Connect database symptoms to the service, release, and workflow that users experience.
  • Keep pool wait, query duration, lock wait, and replication delay as separate phases.
  • Use normalized operation labels and controlled errors instead of raw statements, parameters, or connection details.

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

Database Reliability Monitoring with SQL setup prompt

text
Instrument database reliability with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Add structured events around the application's database boundary for:
1. Completed queries with query_fingerprint, service, database_name, status, duration_ms, rows_returned, release, and environment.
2. Connection-pool samples with active_connections, idle_connections, max_connections, waiting callers, acquisition wait, and timeout outcome.
3. Terminal transactions with transaction_id, status, controlled error_type, duration_ms, and workflow context.
4. Lock waits, replication or CDC lag, and migration outcomes where the application already has an approved signal.

Create a dashboard for slow-query rate, pool wait rate, transaction rollback rate, lock waits, replication lag, and migration failures. Add alerts only after minimum volume and sustained-duration thresholds are reviewed.

Do not log raw SQL parameters, unrestricted statement text, connection strings, credentials, database error dumps, or customer records.

Setup steps

  1. 1Choose one database-dependent workflow and define its safe operation fingerprints.
  2. 2Instrument the application database wrapper, pool, transaction boundary, and migration job.
  3. 3Send synthetic success, timeout, rollback, lock-wait, and lag examples.
  4. 4Review rates and thresholds with the database owner before enabling alerts.

Events to capture

database_query_completeddatabase_pool_sampleddatabase_transaction_completeddatabase_lock_wait_observeddatabase_replication_sampleddatabase_migration_completed

Questions unlocked

  • Which normalized database operations are slow most often?
  • Which pools make callers wait or time out?
  • Did a release change rollback, lock, migration, or replication behavior?

Related SQL recipes

Answer the next question with SQL

Run the query against the structured fields from this workflow, inspect the example result, and turn a useful answer into a dashboard or alert.

Browse all recipes

Next step

Create the API key your agent will use

The free plan is enough to run the prompt, send test events, and review the first dashboard.

Related pages