Add events in application code
Record the operation fingerprint and final status where the application sees pool wait, execution, transaction, and timeout outcomes.
Selection framework
Log where the final result is known
Do not log raw statements
Normalize operations before collection. SQL text, bound parameters, connection strings, and returned rows can expose secrets or customer data.
Connect pressure to customer impact
Include the service, release, route, job, or account so you can see who is affected by pool saturation, cache misses, or consumer lag.
Shared event contract
Use the same field definitions across services
- database_system, operation, query_fingerprint, status, and duration_ms
- pool_name, wait_ms, rows_affected, release, and environment
- account_id, request_id, transaction outcome, and controlled SQLSTATE
Adapt these fields to your workflow. Document units, allowed statuses, and identifiers before several services write to the same table. Name the team responsible for the schema.
Verification
Exercise failure paths before alerts
- 1Run one successful query, timeout, rollback, and pool-wait fixture.
- 2Confirm no SQL parameters, credentials, or returned data enter events.
- 3Compare total application duration with the time spent waiting for a connection and running the query.
- 4Query regressions by operation fingerprint and release.
Implementation guides
Match the framework, provider, or runtime
Setup guide with source links
Supabase and Postgres app telemetry
Track product workflows, database-adjacent jobs, API routes, and customer-facing failures from server code.
Open guideSetup guide with source links
node-postgres pool and query telemetry
Instrument node-postgres query fingerprints, connection acquisition, pool pressure, timeouts, transaction outcomes, and database errors without logging SQL parameters.
Open guideSetup guide with source links
Prisma ORM database telemetry
Measure Prisma operation fingerprints, model and method latency, failures, result counts, releases, and database-dependent workflows without collecting raw query parameters.
Open guideSetup guide with source links
Flask and SQLAlchemy telemetry
Record Flask request results and SQLAlchemy transaction behavior with approved Python event fields, consistent route templates, and safe error categories.
Open guideSetup guide with source links
Redis and node-redis telemetry
Measure Redis command outcomes, latency, cache behavior, reconnects, and bounded error categories alongside node-redis.
Open guideSetup guide with source links
Kafka consumer lag and processing analytics
Monitor Kafka consumer outcomes, partition lag, processing latency, retries, and poison-message handling with structured events.
Open guideSetup guide with source links
MySQL query and pool telemetry
Track normalized MySQL operations, pool wait, transaction outcomes, controlled error categories, and release regressions without storing raw SQL or parameters.
Open guideSetup guide with source links
MongoDB operation telemetry
Track named MongoDB operations, latency, result counts, retries, transaction outcomes, and release regressions without collecting documents or query values.
Open guideVerify one end-to-end workflow first
Create a free API key, choose the closest runtime guide, and send one known success and failure before expanding coverage.