Module 12 · Lesson 24 of 25

Metrics that actually matter

Part of KumoMTA: High-Volume Sending Engine — Observability, Alerting & Deliverability Tuning.

Track these per (tenant, destination, day):

Metric Warning Critical
Delivery rate <95% <90%
Bounce rate (hard) >2% >5%
Complaint rate (FBL) >0.1% >0.3%
Throttle hits (4xx) >5% >20%
Queue depth per destination growing >1h backlog
Auth failures (DKIM/DMARC) >0.1% >1%
Open rate (where measurable) declining <10%

KumoMTA exposes Prometheus metrics on /metrics endpoint (enabled via init.lua HTTP listener). Scrape every 15s.

Sample Grafana panels:

  • Stacked bar of delivery vs bounce vs deferred per destination.
  • Heatmap of complaint rate per tenant per day.
  • Queue depth time series with annotations on shaping changes.

🎯 The metric you should obsess over is complaint rate. Above 0.3% you're in soft-filter territory; above 0.5% you're being blocklisted.

Sign in to keep track of what you have read.

Pulse · self-hosted sending

Own the infrastructure your pipeline depends on.

One install script on your own server. Pulse sets up the MTA, mailboxes, certificates and dashboard; you add domains and start sending.

# on a fresh Ubuntu server
$ cd pulse && sudo ./install.sh
→ docker compose up · kumomta · stalwart · caddy
→ dashboard ready on https://pulse.yourdomain.com
$

Also from us:Beat — monitoring that tells you the fixConsulting — $65/hr, no retainer