# Monitoring plan - identity-email-notifications Decisions (Q4 B, Q5 A): journal plus Sentry on the existing tooling; no new dashboards; no threshold rule. ## Signals (structured log events, never with credentials, addresses, tokens or links) | Event | Level | When | Meaning | |---|---|---|---| | `mail_status enabled=true|false ...` | Information | every start | whether mail is on, with SMTP host, port, STARTTLS and the default sender DOMAIN | | `mail_configuration_invalid: ... {settings}` | **Error** | start, once | an SMTP host is set but the configuration is incomplete or invalid: mail stays OFF; names the settings | | `identity_mail_failed code=auth_failed / rejected_sender / tls_failed / not_configured` | **Error** | per failed mail | configuration problem, somebody has to fix it (wrong credentials, a sender the account may not use, TLS, no host) | | `identity_mail_failed code=timeout_* / rejected_recipient / rejected / connection_failed / unknown` | Warning | per failed mail | passes by itself or concerns one message; journal and breadcrumbs only | | `identity_mail_sent kind=... recipient_domain=...` | Information | per sent mail | volume, no address | | `password_reset_request_ignored`, `password_reset_completed`, `password_reset_request_failed` | Information / Warning | reset flow | cooldown hits, completed resets | ## Alerting (Sentry, existing project of each site, notification by e-mail to the project owner) Sentry turns Error events into issues. Create one rule per environment (test and production) in the site's Sentry project: - **Rule "mail configuration problem"**: when an issue is created or reopened and its message contains `identity_mail_failed` or `mail_configuration_invalid` (level Error), notify the project owner by e-mail. No frequency threshold (Q4 B). Nothing else: timeouts and recipient problems are not alerted. ## Where to look - Pi: `journalctl --user -u | grep -E "mail_status|identity_mail_|mail_configuration_invalid"`. - IIS (later): the stdout log or the event log of the app pool (to be settled in the ASF-production work). - Sentry: issues filtered on `environment:`.