Logs & analytics
Every email request is logged - success or failure, SDK or test send. Logging is not a debugging afterthought here; it is a core feature of the platform.
What a log row contains
| Field | Notes |
|---|---|
| Status | SUCCESS or FAILED - failures are first-class rows, not missing data. |
| Recipient | The address the send targeted. |
| Template | Slug used for the send; kept even if the template is later deleted. |
| Sender | The project's sender identity at send time. |
| Provider | Which provider handled it (resend, dev…). |
| Error | The exact provider or validation error on failure. |
| Message id | Provider's id, for cross-referencing deliverability. |
| Timestamp | When the platform processed the request. |
Finding things
The Logs view in each project supports free-text search (recipient, template slug, error text), status and template filters, and pagination. The common workflow: a user reports a missing email - search their address, read the status, read the error, done. No SSH, no application-server logs.
Analytics
The dashboard overview aggregates across your projects; each project also has its own view. Both show:
- Total volume and last-24-hour volume
- Success and failure rates
- Emails per day for the last 14 days, split by outcome
- Most-used templates
- Per-project distribution (overview only)
Coming later
Retry history, provider delivery status (webhooks), and log export are on the roadmap - the log schema already reserves room for them.