Mislukte mails door een configuratieprobleem (auth_failed, rejected_sender, tls_failed, not_configured) worden als Error gelogd zodat Sentry een alert stuurt; timeouts en ontvangerproblemen blijven Warning. Documentatie: uitrol per host met de hand in shared/env, rollback, monitoringplan, checklist; ASF-productie op IIS als open punt voor een latere feature. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Monitoring setup - identity-email-notifications
Done in code (this feature)
- The log level follows the kind of failure: Error for configuration problems (
auth_failed,rejected_sender,tls_failed,not_configured), Warning for the rest, so Sentry alerts only when somebody has to act. Tested (SmtpSenderDiagnosticsTests: wrong login and refused sender are Error events, refused recipient and timeouts stay Warning; level mapping for every code; no secret in any line). - A start-up line states whether mail is on, and an Error names every missing or invalid setting when it is not.
To be done by a person (the assistant does not change shared Sentry projects)
- In the Sentry project of ASF (environment
test) and of SlpSoftware (environmentstest, laterproduction): create the issue-alert rule of the monitoring plan (message containsidentity_mail_failedormail_configuration_invalid, notify the owner by e-mail). Thesentry:sentry-create-alertskill can create it on request, with Bryan's go. - Check once per host after switching mail on: the journal shows
mail_status enabled=true. - Trigger the alert once on test (for example a wrong password in
shared/envfor a minute) to see that the e-mail arrives; restore the password.
Runbook lines (Q5 A)
After any change of mail settings: restart, read the journal for mail_status enabled=true or mail_configuration_invalid, check /System/capabilities for emailEnabled.