Integration · APM & alerting

Email (SMTP)

STARTTLS on 587, batch grouping, reply chains.

What gets collected

SMTP with STARTTLS. When the channel has group_window_seconds > 0, events are grouped into a single digest. Optionally, reply-to is set for thread-style replies.

Requirements

  • SMTP host/port
  • STARTTLS (587)
  • credentials in API env

Key metrics

Collected out of the box. Every metric is available in dashboards, alerts and PromQL.

email.sentemail.bounce.rateemail.digest.grouped

Setup steps

  1. 1SMTP_HOST / PORT / USER / PASS in the API env
  2. 2Per-channel recipients plus an optional group window

After install

  • · Metrics show up on the dashboard within 15-30 seconds
  • · Integration labels flow into filters automatically
  • · Dashboard presets for common metrics are available in the editor
More in the docs
Email (SMTP)
Open the guide →

Frequently asked questions

What does Unimoni collect from Email (SMTP)?
STARTTLS on 587, batch grouping, reply chains. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Email (SMTP) and everything else in one place.
How long does it take to connect Email (SMTP)?
Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
What access does the Email (SMTP) integration need?
Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
Is Email (SMTP) monitoring available self-hosted and on the free plan?
Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.

Similar integrations