Telemetry
Copy-paste instrumentation template

Webhook Debugging Template

Track delivery, processing, retries, provider status, idempotency, and downstream effects for critical webhooks.

Questions this unlocks
  • Which provider events fail most often?
  • Are retries fixing failures or creating duplicates?
  • Which downstream jobs are triggered by each webhook type?

Template

Paste this into your coding agent

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

webhook-debugging

Webhook Debugging Template

text
Instrument webhook handling with Telemetry.

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

Log webhook_received, webhook_processed, webhook_failed, webhook_retried, and webhook_deduplicated with:
provider, event_type, route_template, status, status_code, latency_ms, attempt, idempotency_outcome, downstream_job_count, team_id, and error_type.

Create queries for volume by provider, failures by event_type, retry rate, duplicate rate, p95 processing time, and latest failed webhooks.

Do not log raw webhook bodies, signatures, secrets, payment details, or personal data.

Events to capture

webhook_receivedwebhook_processedwebhook_failedwebhook_retriedwebhook_deduplicated

More templates