Inbound Monitoring and Recovery
Why You Would Use This
Section titled “Why You Would Use This”Inbound operations have two different failure surfaces, and you need visibility into both:
- Ingest validation failures (
rejections): request was blocked and never forwarded. - Forwarding delivery failures (
pending_retry/failed_permanent): request was accepted, but downstream delivery had issues.
Monitoring both surfaces makes incident response faster because you can quickly tell whether the problem is provider/auth configuration or destination availability.
Console Workflow
Section titled “Console Workflow”- Open Messages and switch to inbound direction.
- Review message statuses to track retry backlog and permanent failures.
- Review Rejections for ingest-side validation failures.
- Use endpoint filters to isolate one integration at a time.
- Apply recovery actions (
replay,replay-all,pause,resume) as needed.
API Workflow
Section titled “API Workflow”API reference:
- Get inbound logs
- Get inbound metrics
- Get inbound time-series metrics
- List inbound rejections
- Replay inbound message
1) Monitor forwarding health
Section titled “1) Monitor forwarding health”curl "https://api.hookbridge.io/v1/inbound-logs?limit=50" \ -H "Authorization: Bearer YOUR_API_KEY"
curl "https://api.hookbridge.io/v1/inbound-metrics?window=24h" \ -H "Authorization: Bearer YOUR_API_KEY"
curl "https://api.hookbridge.io/v1/inbound-metrics/timeseries?window=24h&inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID" \ -H "Authorization: Bearer YOUR_API_KEY"2) Monitor ingest verification failures
Section titled “2) Monitor ingest verification failures”curl "https://api.hookbridge.io/v1/inbound-rejections?limit=50&inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID" \ -H "Authorization: Bearer YOUR_API_KEY"3) Recover failures
Section titled “3) Recover failures”curl -X POST https://api.hookbridge.io/v1/inbound-messages/YOUR_INBOUND_MESSAGE_ID/replay \ -H "Authorization: Bearer YOUR_API_KEY"Recommended Runbook Pattern
Section titled “Recommended Runbook Pattern”- Check rejections first if expected inbound volume drops.
- Check retry/failure statuses if inbound volume is normal but downstream side effects are missing.
- Confirm the fix with one replayed message.
- Use replay-all for broader recovery only after validation.
Personalize Examples
Enter your credentials to populate code examples throughout the docs.