Notifications & Alerts
Mitte proactively monitors your webhook infrastructure and sends alerts when something needs attention. Notifications are delivered via multiple channels and configurable per-user.
Notification Types
Anomaly Detected
Triggered when the failure rate for an endpoint spikes above normal levels. Mitte runs anomaly detection every 10 minutes using a Z-score algorithm over a 48-hour sliding window of hourly stats.
An alert fires when:
- Z-score > 2.5 (statistically significant deviation), OR
- Failure rate > 80% with at least 10 requests in the hour
At least 6 hours of historical data are required before anomaly detection activates for a new endpoint.
Quota Warning
Triggered when you reach 90% of your monthly webhook request quota. This gives you time to upgrade your plan or reduce traffic before hitting the hard limit.
| Plan | Warning Threshold | Hard Limit |
|---|---|---|
| Free | 4,500 requests | 5,000 requests |
| Pro | 225,000 requests | 250,000 requests |
Endpoint Down
Triggered when an endpoint accumulates 5 consecutive delivery failures. This usually indicates that your target server is down or misconfigured.
The failure counter resets on:
- A successful delivery
- 1 hour of inactivity
Trial Ending
Triggered when your 14-day Pro trial is about to expire, giving you time to subscribe or prepare for the transition to the Free plan.
Delivery Channels
| Channel | Default | Description |
|---|---|---|
| In-app | Always on | Notifications appear in the dashboard bell icon and are pushed in real-time via SSE. |
| Enabled | Sent from [email protected] via Resend. | |
| Outbound webhook | Disabled | POST to a URL you configure. Useful for Slack/Discord integrations or custom automation. |
Configure notification preferences from the Notifications page in your dashboard.
Outbound Webhook Format
When the outbound webhook channel is enabled, Mitte sends a POST request with a JSON body:
{
"type": "ANOMALY_DETECTED",
"title": "Failure rate spike detected",
"message": "Endpoint 'stripe-prod' failure rate spiked to 85% (z-score: 3.2)",
"endpointSlug": "mt_abc123",
"timestamp": "2026-02-13T10:30:00.000Z"
}
The outbound webhook has a 5-second timeout and is protected against SSRF (internal/private IP addresses are blocked).
Real-time Updates
All notifications are delivered in real-time via Server-Sent Events (SSE). When you're viewing the dashboard, new webhook deliveries and notifications appear instantly without polling.
Two event types are published:
webhook:delivered— emitted after every delivery (success or failure)notification:created— emitted when a new notification is created
The SSE connection automatically reconnects if interrupted.