OpsProbe

Release notes

OpsProbe v0.3.4: alert delivery.

Released on August 20, 2026, v0.3.4 turns the existing alert outbox into a safe, observable email delivery path.

Release date August 20, 2026Version v0.3.4Type minor

Quick answer

Incident-open, recovery, and escalation events can now use SMTP delivery with claim protection, bounded retries, delivery status, and failure context.

What changed

  • Added an alert delivery worker around the existing alert_events outbox.
  • Added safe row claiming with UUID claim tokens to prevent duplicate sends across workers.
  • Added attempt count, retry time, last attempt, claim state, and last error metadata.
  • Added bounded exponential retry behavior for transient SMTP failures.
  • Added visible sent, failed, sending, and pending delivery states to the Alerts view.
  • Included the Docs and console UI fixes deployed after v0.3.3.

Configuration

Email delivery is disabled by default. Enable it only after choosing and verifying a provider.

  • OPSPROBE_EMAIL_ENABLED=true enables delivery.
  • OPSPROBE_SMTP_HOST and OPSPROBE_SMTP_FROM are required.
  • STARTTLS on port 587 is the default; implicit TLS and a loopback-only plaintext test mode are supported.
  • SMTP username and password must be configured together.

Verification

  • Rust formatting, check, tests, and release build passed.
  • PostgreSQL integration test passed against an isolated temporary database.
  • Controlled SMTP test passed against a local loopback listener and verified the message envelope and content.
  • Frontend syntax, diff, Docs navigation, and sitemap checks passed.

Known limits

Production email delivery remains disabled until explicit SMTP credentials are configured. Billing, internal analytics, multi-region probes, business-flow monitoring, deep security scanning, and AI analysis remain future work.