Measure Webhook debugging and check the results
To measure webhook debugging, choose one workflow and its owner. Define the events, test them with known inputs, and write a query that answers a specific question.
- 1
Choose when to log
Log webhook_received, webhook_processed, webhook_failed, and webhook_retried.
- 2
Capture the outcome
Begin with webhook_received, webhook_processed, webhook_failed and document the grain of each event.
- 3
Check the stored rows
Create alerts for repeated failures, retry spikes, and processing latency.
- 4
Make the decision
Which webhook event types fail most often?
Use case versus template
Choose what to measure
Use this guide to choose what to measure and when to log it. For a shorter setup prompt, open the matching template.
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.
Webhook debugging setup prompt
Instrument webhook debugging with Telemetry.
Use /skill.md and this Telemetry API key: YOUR_API_KEY
Please log webhook_received, webhook_processed, webhook_failed, webhook_retried, and webhook_deduplicated. Include 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.Setup steps
- 1Log webhook_received, webhook_processed, webhook_failed, and webhook_retried.
- 2Capture provider, event type, status, latency, attempt, and idempotency outcome.
- 3Connect downstream jobs or billing syncs triggered by each webhook.
- 4Create alerts for repeated failures, retry spikes, and processing latency.
Events to capture
Questions you can answer
- Which webhook event types fail most often?
- Are retries fixing failures or creating duplicates?
- Which downstream systems are affected by provider delays?
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.
Measure webhook retry recovery
Are webhook retries recovering failures or creating more work?
Open recipeMeasure webhook latency and duplicate rate
Which webhook sources are slow, duplicated, or unreliable?
Open recipeMeasure webhook end-to-end completion
Which webhook types finish their downstream work within five minutes?
Open recipeCustomer evidence
Related customer stories
"Telemetry is one of the easiest ways to go from dumping in your data to actually understanding it."
Shayan Taslim, LogSnag
Read the customer story"Telemetry is my go-to for dumping logs and tracking events. It's straightforward, the SQL workbench is fast, and I don't have to worry about the schema upfront. Running SQL over a REST API lets me fetch data and dump reports straight to Slack. It's the essentials of what Sentry did for me."
Prem Viswanathan, SwiftCX
Read the customer storyNext 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