Follow one logical job across attempts
Keep a stable job identifier and separate attempt-level events from the final outcome so retry recovery remains measurable.
Selection framework
Log where the final result is known
Separate queue wait from execution
Scheduled, enqueued, started, and completed timestamps distinguish backlog pressure from slow worker code.
Define terminal states
Document completed, permanently failed, cancelled, discarded, and dead-letter outcomes before writing stalled-job queries or alerts.
Shared event contract
Use the same field definitions across services
- job_id, job_name, queue_name, status, attempt, and release
- scheduled_at, started_at, completed_at, duration_ms, and wait_ms
- error_type, worker_name, item_count, dead_lettered, and account_id
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 success, retry recovery, permanent failure, and cancellation fixture.
- 2Confirm the same logical job remains correlated across attempts.
- 3Reconcile queue wait, execution duration, and end-to-end duration.
- 4Test duplicate delivery and idempotent downstream behavior.
Implementation guides
Match the framework, provider, or runtime
Setup guide with source links
Inngest and Trigger.dev job telemetry
Instrument async workers, scheduled jobs, retries, failures, and dead-letter events with SQL-ready logs.
Open guideSetup guide with source links
Django and Celery structured event monitoring
Connect Django request outcomes and Celery task lifecycles with safe identifiers, latency, retries, and final status.
Open guideSetup guide with source links
Temporal workflow observability
Track Temporal workflow outcomes, activity retries, schedule-to-start latency, and business milestones without recording workflow payloads.
Open guideSetup guide with source links
n8n workflow telemetry
Use the n8n HTTP Request node to send approved fields for workflow completion, failure, retries, item counts, and downstream delivery results to Telemetry.
Open guideSetup guide with source links
BullMQ queue monitoring
Measure BullMQ queue wait, execution duration, retries, failures, and dead-letter growth with SQL-ready lifecycle events.
Open guideSetup guide with source links
AWS SQS queue observability
Track SQS message age, receive attempts, processing outcomes, batch behavior, and dead-letter routing without storing message bodies.
Open guideSetup guide with source links
RabbitMQ queue telemetry
Track RabbitMQ publish confirmation, delivery, acknowledgement, redelivery, queue wait, retries, and dead-letter outcomes with structured events.
Open guideSetup guide with source links
Google Cloud Pub/Sub telemetry
Track Pub/Sub publish, delivery, acknowledgement, redelivery, ordering, queue age, and dead-letter outcomes with stable message identifiers.
Open guideSetup guide with source links
Azure Service Bus telemetry
Track Azure Service Bus sends, receives, lock renewal, settlement, redelivery, deferral, and dead-letter outcomes without collecting message bodies.
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
Sidekiq job telemetry
Track Sidekiq execution outcomes, attempts, queue wait, errors, and releases from server middleware without copying job arguments.
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
AWS Lambda structured event monitoring
Track Lambda invocations, cold starts, duration, retries, and business outcomes with compact structured events.
Open guideSetup guide with source links
Stripe webhook telemetry
Debug payment, subscription, invoice, retry, and downstream billing sync behavior without storing webhook bodies.
Open guideSetup guide with source links
GitHub Actions workflow telemetry integration
When a GitHub Actions workflow finishes, send its run, attempt, job, conclusion, duration, and release fields.
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.