Telemetry
Copy-paste instrumentation template

Background Job Failure Monitor

Capture queue, cron, import, billing sync, and webhook job health from the first run through retries and failures.

Questions this unlocks
  • Which jobs are failing repeatedly?
  • Which queues are falling behind?
  • Which job names have the worst p95 duration?

Template

Paste this into your coding agent

Replace YOUR_API_KEY, run the flow locally, then verify the generated events and dashboards.

job-failure-monitor

Background Job Failure Monitor

text
Instrument background jobs with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Log job_started, job_completed, job_failed, job_retried, and dead_letter_created with:
job_name, queue_name, attempt, status, duration_ms, scheduled_at, started_at, completed_at, item_count, retry_count, worker_name, and error_type.

Create queries and a dashboard for throughput by job, failures by job, p95 duration, retry volume, stalled jobs, and newest dead-letter events.

Do not log raw job payloads, credentials, webhook bodies, or customer content.

Events to capture

job_startedjob_completedjob_failedjob_retrieddead_letter_created

More templates