MonsterOps logo MonsterOps
Docs / Alerting / Notifications

Notifications

Overview

Notifications send alerts through configured channels (email/SMTP, webhooks) when a rule fires — with thresholds and cooldown periods so you're told about what matters without being flooded.

Where things are

  • Channels — where alerts go: SMTP email and/or webhook endpoints.
  • Rules — what triggers an alert, the threshold that must be crossed, and a cooldown period to suppress repeats.
  • History — past notifications (pruned by the Log Retention job — see Scheduler).

Common tasks

  • Email on a condition — add an SMTP channel (needs MONSTEROPS_SMTP_* in Configuration), then a rule with a threshold and cooldown.
  • Push to an external system — use a webhook channel (see Webhooks for signing and the event stream).
  • Stop repeat spam — raise the cooldown on a noisy rule.

Problems you may hit

  • No emails arrive — SMTP isn't configured or is wrong; verify MONSTEROPS_SMTP_HOST/PORT/USER/ PASSWORD/FROM/TLS. Check the app log for send errors.
  • Too many alerts — the threshold is too low or cooldown too short.
  • Nothing fires — the rule's condition never crosses its threshold; confirm the underlying data actually reaches it.