Alerts
Alerts notify you when something goes wrong with your webhooks — a missing delivery, a spike in errors, or unusual traffic patterns. You define alert conditions on an endpoint, and CatchHook evaluates them continuously.
Note: Alerts and signature verification are currently available for webhook endpoints only. Email endpoints do not support alerts or signature configuration. Email authentication (SPF, DKIM, DMARC) is handled at the transport level by AWS SES and displayed on the email event detail page.
Alert types
Pro plan
| Type | What it detects |
|---|---|
| Missing webhook | No webhook received within a specified time window (e.g., 30 minutes) |
| Error response | Forwarding or replay returns a non-2xx status code |
| Signature failure rate | Percentage of requests with failed signature verification exceeds threshold |
| Signature missing rate | Percentage of requests missing expected signature headers exceeds threshold |
Business plan (includes all Pro types)
| Type | What it detects |
|---|---|
| Keyword match | A specific keyword appears in request headers or body |
| Volume spike | Traffic exceeds a threshold compared to baseline |
| Forwarding failure rate | Percentage of forwarding failures exceeds a threshold over a time window |
| Forwarding latency spike | Average forwarding response time exceeds a threshold |
| Tunnel failure rate | Percentage of tunnel delivery failures exceeds a threshold |
| Tunnel latency spike | Average tunnel delivery latency exceeds a threshold |
Creating an alert
- Open an endpoint and expand the Alerts configuration panel.
- Click Add alert rule to expand the form.
- Choose an alert type and configure the condition (thresholds, time windows, keywords).
- Select which notification channels should receive the alert.
- Save.
You can also manage all alerts across endpoints from the Alerts page in the sidebar.
Alert instances
When an alert condition is met, CatchHook creates an alert instance — a record of that specific firing. Each instance has a status:
| Status | Meaning |
|---|---|
| Active | The condition was detected and hasn't been addressed yet |
| Acknowledged | Someone on your team has seen it and is investigating |
| Snoozed | Temporarily silenced — will re-alert if the condition persists after the snooze period |
| Resolved | The issue has been handled |
Managing instances
- Acknowledge — signals to your team that someone is looking at it.
- Snooze — pauses notifications for a set duration.
- Resolve — closes the instance.
Endpoint alert panel
The alerts panel on each endpoint page is split into two sections:
- Open Instances (top) — a table of active, acknowledged, and snoozed instances with inline Acknowledge/Resolve buttons. A "View all instances" link opens the global alerts page filtered to that endpoint.
- Alert Rules (below) — the list of configured alerts with an expandable "Add alert rule" form.
When there are active alert instances, the alerts panel auto-opens and shows an amber badge in the panel header. The endpoint's health header also displays a "Needs attention" state with a recommended action to view alerts.
Notify next request
Enable Notify next request in the quick-actions bar on the endpoint page to receive a one-time notification when the next webhook arrives at that endpoint. Once delivered, the flag automatically turns off. This is useful for confirming a provider is sending data or that a fix has taken effect.
Manual trigger
You can manually trigger any alert from its detail page to test your notification pipeline without waiting for real conditions to be met.
Viewing alert history
The global Alerts page has two views:
- Instances — all alert instances across your account with filters for status, condition type, endpoint, and time window. Supports bulk actions (acknowledge, snooze, resolve).
- Rules — all configured alert rules with their current status and open instance counts.