Agent prompt
Paste this into your coding agent
Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.
agent prompt
Background Job Monitoring setup prompt
text
Instrument background jobs and async workers with Telemetry.
Use /skill.md and this Telemetry API key: YOUR_API_KEY
Please log job_started, job_completed, and job_failed events with job_name, queue_name, attempt, status, duration_ms, scheduled_at, started_at, completed_at, item_count, retry_count, and error_type.
Create a dashboard showing throughput by job, failures by job, p95 duration, retry volume, oldest pending job, and dead-letter events. Add alerts for stalled jobs and repeated failures.Setup steps
- 1Log job_started, job_completed, job_failed, and job_retried.
- 2Include queue, job name, attempt, duration, item count, and error type.
- 3Build a dashboard for throughput, failures, retries, and p95 duration.
- 4Add alerts for stalled jobs, repeated failures, and dead-letter creation.
Events to capture
job_startedjob_completedjob_failedjob_retrieddead_letter_createdcron_tick_failed
Questions unlocked
- Which jobs fail or retry most often?
- Which queues are falling behind?
- Which customers are affected by failed background work?
Next step
Create the API key your agent will use
The free plan is enough to run the prompt, send test events, and review the first dashboard.
Related pages
Claude Code Observability
Give Claude Code a prompt that makes telemetry part of the implementation pass instead of a separate cleanup project.
Open pageCursor Telemetry Setup
A copyable setup prompt for adding event tables, funnel tracking, and dashboards from inside Cursor.
Open pageCodex Instrumentation Prompt
A focused prompt that asks Codex to instrument the rest of the product, verify events, and summarize coverage gaps.
Open page