Choose the terminal middleware boundary
Record requests after the final status and duration are known, and record jobs after the worker knows whether work completed, retried, or failed.
Selection framework
Choose the boundary that knows the result
Keep credentials server-only
Initialize one shared client in server code. Browser and edge collection should pass through an application-owned allowlist.
Preserve framework context without raw payloads
Use route templates, named operations, queue names, and error categories instead of URLs, request bodies, SQL text, or exception dumps.
Shared event contract
Keep the first schema interoperable
- route_template or job_name, status, duration_ms, and release
- request_id, job_id, account_id, and controlled error_type
- environment, runtime, retry_count, and dependency
Adapt these fields to the workflow, but keep units, status categories, identifiers, and ownership explicit before several services depend on the same table.
Verification
Exercise failure paths before alerts
- 1Send one successful and one failed request or job from the actual runtime.
- 2Confirm initialization is reused instead of creating a client per event.
- 3Test shutdown, timeout, and retry behavior for the delivery path.
- 4Query the latest rows by route, job, release, and status.
Implementation guides
Match the framework, provider, or runtime
Sourced implementation guide
Node.js and Express Structured Logging
Instrument Express route outcomes with stable route templates, status codes, request latency, and safe correlation fields.
Open guideSourced implementation guide
Next.js Server Event Analytics
Send SQL-ready events from Next.js route handlers and server actions without exposing an ingestion key to the browser.
Open guideSourced implementation guide
NestJS Request and Workflow Telemetry
Instrument NestJS controllers and providers with normalized route outcomes, latency, errors, releases, and approved account context.
Open guideSourced implementation guide
Cloudflare Worker Telemetry
Log edge request status, latency, provider failures, cron runs, and queue workers from Cloudflare Workers.
Open guideSourced implementation guide
AWS Lambda Structured Event Monitoring
Track Lambda invocations, cold starts, duration, retries, and business outcomes with compact structured events.
Open guideSourced implementation guide
Google Cloud Run Telemetry
Track Cloud Run request and job outcomes, cold-start context, instance concurrency, retries, latency, and releases with application-owned structured events.
Open guideSourced implementation guide
Azure Functions Telemetry
Track Azure Functions HTTP, timer, queue, and event-trigger outcomes with invocation, retry, latency, release, and customer-impact context.
Open guideSourced implementation guide
Inngest And Trigger.dev Job Telemetry
Instrument async workers, scheduled jobs, retries, failures, and dead-letter events with SQL-ready logs.
Open guideSourced implementation guide
BullMQ Queue Monitoring
Measure BullMQ queue wait, execution duration, retries, failures, and dead-letter growth with SQL-ready lifecycle events.
Open guideSourced implementation guide
RabbitMQ Queue Telemetry
Track RabbitMQ publish confirmation, delivery, acknowledgement, redelivery, queue wait, retries, and dead-letter outcomes with structured events.
Open guideSourced implementation guide
Google Cloud Pub/Sub Telemetry
Track Pub/Sub publish, delivery, acknowledgement, redelivery, ordering, queue age, and dead-letter outcomes with stable message identifiers.
Open guideSourced implementation guide
Azure Service Bus Telemetry
Track Azure Service Bus sends, receives, lock renewal, settlement, redelivery, deferral, and dead-letter outcomes without collecting message bodies.
Open guideSourced implementation guide
Stripe Webhook Telemetry
Debug payment, subscription, invoice, retry, and downstream billing sync behavior without storing webhook bodies.
Open guideSourced implementation guide
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 guideSourced implementation guide
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 guideSourced implementation guide
Redis and node-redis Telemetry
Measure Redis command outcomes, latency, cache behavior, reconnects, and bounded error categories alongside node-redis.
Open guideSourced implementation guide
Pino Structured Event Analytics
Pair Pino diagnostic logs with bounded Telemetry outcome events for Node.js request, job, and product reliability analysis.
Open guideSourced implementation guide
Winston Structured Event Analytics
Connect Winston application diagnostics to small SQL-ready request, workflow, and job outcomes without duplicating the entire log stream.
Open guideSourced implementation guide
Vercel AI SDK Telemetry
Track streaming completions, token usage, retries, latency, and accepted results from AI SDK workflows.
Open guideSourced implementation guide
OpenAI Responses API Telemetry
Measure OpenAI Responses API latency, token usage, tool activity, failures, and downstream outcomes without collecting prompts or generated content.
Open guideSourced implementation guide
Mastra Agent Telemetry
Track Mastra agent and workflow outcomes, tool activity, latency, retries, cost, and product acceptance alongside built-in traces and evals.
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.