Email Is Infrastructure. Start Treating It Like One.

For most people, email is a UI experience. You open Gmail or Yahoo, click Compose, write a subject and body, add a recipient, and hit send. From an application perspective, email behaves more like infrastructure. Messages pass through external providers, delivery happens asynchronously, and a single send can trigger multiple downstream events. But if email is infrastructure, can it be made observable like the rest of an application? Yes. By converting email lifecycle events into telemetry. This guide shows how to do that. Using Resend webhooks and OpenTelemetry (OTel), email events (sent, delivered, bounced, complained) become traces and metrics visible alongside the rest of your application telemetry. How It Works Resend fires a webhook for every email event. A lightweight webhook receiver picks it up and emits a OpenTelemetry span and metric. This guide uses SigNoz as the observability backend, but the same setup should work with any OTLP compatible vendor . Your App → Resend API ↓ R