Send and verify events with Inngest and Trigger.dev job telemetry
Use Inngest and Trigger.dev job 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
Background job monitoring
- 2
Define the contract
provider, job_name, run_id, queue_name, and trigger_type
- 3
Log the final result
Emit attempt events only when attempt-level analysis is required, and emit one separate final event so retries cannot inflate completed-job counts.
- 4
Check the stored event
Exercise a known fixture, then inspect job_completed for one correctly typed terminal row.
Before you start
Before you start
- An Inngest function or Trigger.dev task with stable function, task, and run identifiers
- Lifecycle hooks or final handlers that observe success, exhausted retries, and cancellation
- Idempotent side effects and an explicit distinction between an attempt and the final run outcome
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.
Inngest and Trigger.dev job telemetry event
await telemetry.log("job_completed", {
provider: "inngest",
job_name: "sync_stripe_subscription",
run_id: runId,
queue_name: "billing",
attempt: 1,
status: "success",
duration_ms: 4120,
item_count: 37,
retry_exhausted: false,
release: process.env.APP_RELEASE,
});Event schema
provider, job_name, run_id, queue_name, and trigger_type
attempt, status, duration_ms, scheduled_at, started_at, and error_type
item_count, retry_exhausted, idempotency_outcome, and release
Check your setup
Checkpoint 1
Emit attempt events only when attempt-level analysis is required, and emit one separate final event so retries cannot inflate completed-job counts.
Checkpoint 2
Use provider lifecycle or failure hooks for exhausted retries; a caught step error is not necessarily a failed function or task.
Checkpoint 3
Test replay and retry behavior with an idempotent fixture so monitoring does not conceal duplicate side effects.
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.
Inngest and Trigger.dev job telemetry verification query
SELECT *
FROM job_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 Alerts
Add a threshold and recipients to your reliability query to get alerts.
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.
Reconstruct a correlated workflow timeline
What happened, in order, during the latest failed workflow?
Open recipeMeasure background job retry and failure rate
Which background jobs consume the most retries or still fail?
Open recipeFind stalled background jobs with SQL
Which jobs started but never produced a final event?
Open recipeMeasure queue wait time by job
Which jobs wait longest before a worker starts them?
Open recipeMeasure dead-letter queue growth
Which queues are adding dead-letter jobs faster than they are resolving them?
Open recipeDetect missed cron schedules
Which scheduled jobs ran later than their documented interval?
Open recipeDetect background-job retry storms
Which job types are spending the most work on retries right now?
Open recipeBrowse by implementation family
Compare related integration patterns
Templates to pair with this integration
Background job failure monitor
Capture queue, cron, import, billing sync, and webhook job health from the first run through retries and failures.
Open templateAI agent security audit template
Record tool authorization decisions, policy versions, human approvals, and final outcomes. Use selected event fields to keep sensitive payloads out.
Open templateAI agent observability template
Track agent runs, tool calls, retries, latency, errors, and accepted outputs in event tables you can query with SQL.
Open templateMore integrations
Sidekiq job telemetry
Track Sidekiq execution outcomes, attempts, queue wait, errors, and releases from server middleware without copying job arguments.
Open guideTemporal workflow observability
Track Temporal workflow outcomes, activity retries, schedule-to-start latency, and business milestones without recording workflow payloads.
Open guideBullMQ queue monitoring
Measure BullMQ queue wait, execution duration, retries, failures, and dead-letter growth with SQL-ready lifecycle events.
Open guide