Send and verify events with MySQL query and pool telemetry
Use MySQL query and pool telemetry where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.
- 1
Choose the outcome
Slow-query analysis
- 2
Define the contract
database_system, operation, query_fingerprint, pool_name, and release
- 3
Log the final result
Measure pool acquisition and query execution separately in the application so the event records both durations.
- 4
Check the stored event
Exercise a known fixture, then inspect mysql_query_completed for one correctly typed terminal row.
Before you start
Before you start
- A server-side MySQL client such as mysql2 and telemetry-sh
- An allowlisted operation-name or query-fingerprint function owned by the application
- Reviewed handling for SQLSTATE values, timeouts, transactions, and pool acquisition
Delivery setup
Install and initialize server-side
Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.
npm installation
npm install telemetry-sh- 1Create one reusable server-side client. Set its timeout and retry limit.
- 2Log an event when the operation succeeds, fails, retries, or times out.
- 3Send test events with known results and inspect the stored rows before enabling an alert.
Snippet
Start with one structured event
Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.
MySQL query and pool telemetry event
await telemetry.log("mysql_query_completed", {
database_system: "mysql",
operation: "account_entitlements.select",
query_fingerprint: "account_entitlements_by_account_v2",
pool_name: "primary",
status: "success",
wait_ms: poolAcquiredAt - startedAt,
duration_ms: completedAt - startedAt,
rows_affected: result.length,
transaction_status: "not_started",
route_template: "/api/accounts/:accountId/entitlements",
release: process.env.APP_RELEASE,
});Event schema
database_system, operation, query_fingerprint, pool_name, and release
status, duration_ms, wait_ms, rows_affected, and transaction_status
controlled_sqlstate, retry_count, route_template, job_name, and account_id
Check your setup
Checkpoint 1
Measure pool acquisition and query execution separately in the application so the event records both durations.
Checkpoint 2
Prefer an application-owned operation name or reviewed digest; never send raw SQL, bound values, connection strings, returned rows, or unrestricted error text.
Checkpoint 3
Use MySQL Performance Schema for database diagnostics. Send application outcomes to Telemetry and join them with customer activity.
Verification
Prove the event arrived
Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.
MySQL query and pool telemetry verification query
SELECT *
FROM mysql_query_completed
ORDER BY timestamp_utc DESC
LIMIT 20;Implementation references
Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.
Where to log
Keep the outcome event small and recoverable
This pattern provides
- Record the outcome as an event you can query with SQL.
- Stable fields for dashboards, alerts, and cross-event correlation.
- Test events for checking success, failure, retries, and timeouts.
This pattern does not provide
- An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
- Exactly-once delivery merely because the payload contains an event ID.
- Permission to collect raw provider payloads, user content, credentials, or regulated data.
Example event schemas
Event schemas for this workflow
Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.
Use these queries in Telemetry
Learn about SQL query API
Run read-only DataFusion SQL over structured-event tables and reuse the result.
Related SQL recipes
More SQL recipes
Run the query using this workflow's event fields and check the example result. Save the result to a dashboard or set up an alert.
Find slow database queries by fingerprint
Which database operations are consistently slow enough to investigate?
Open recipeMeasure database connection-pool saturation
Which application pools are making callers wait for a database connection?
Open recipeCalculate database transaction rollback rate
Which services roll back an unusual share of database transactions?
Open recipeAnalyze database errors by SQLSTATE and release
Which database error classes increased after an application release?
Open recipeRank database queries by total time impact
Which database operation consumes the most cumulative request time?
Open recipeBrowse by implementation family
Compare related integration patterns
Templates to pair with this integration
More integrations
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 guidePrisma 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 guideMongoDB operation telemetry
Track named MongoDB operations, latency, result counts, retries, transaction outcomes, and release regressions without collecting documents or query values.
Open guide