Design for delivery
Sign every webhook, include event IDs, and retry with exponential backoff and jitter.
Expose receipt endpoints so customers know you got their acknowledgment.
If you promise uptime updates, your webhook pipeline must have its own SLO.
Monitor the path
Use Watch.Dog synthetics to call customer-facing test endpoints and measure latency and failures.
Alert on retry exhaustion, signature failures, and sudden target error spikes.
Coordinate with status pages
Publish incident webhooks at the same time you update the status page to avoid message drift.
Batch low-severity updates to prevent rate limits during noisy incidents.