Amazon SES error alerts

Send first-occurrence alerts and digest emails without mailing every repeated error.

Logister uses standard Rails SMTP settings, so self-hosted teams can send branded project error emails through Amazon SES or another SMTP provider while Sidekiq handles delivery outside the web request.

Notification cadence

Alert on new error types, summarize repeats.

First-occurrence emails help teams notice new grouped errors. Daily or weekly digests summarize project activity so repeat occurrences stay visible without creating inbox noise.

  • First occurrence alerts are for new grouped error types.
  • Digest emails summarize unresolved project activity over a chosen cadence.
  • Project users can choose the alert style that fits their role.

Email delivery

SES is configured through ordinary SMTP environment variables.

Logister does not need checked-in provider secrets. Self-hosters put SMTP host, port, domain, username, password, sender, and reply-to values in their deploy provider's secret/config store. The deployment reference explains each sample entry and which provider values to use.

Read the deployment environment reference.

Deliverability

Branded, useful mail is less likely to be treated as noise.

Error emails include project, environment, release, occurrence, and triage links when available. That helps recipients understand why the message was sent and makes the email more useful than a generic exception dump. Operators should also configure SES identity verification, SPF, DKIM, DMARC, and a sending domain that matches the self-hosted instance.

Worker requirement

Keep Sidekiq running for alerts and digests.

Email delivery, first-occurrence alerts, and digest scheduling run through background jobs. A self-hosted deployment should run at least one Sidekiq worker alongside the Rails web process.

Read the Docker and worker process overview.