Files

master c58a236d70 Doctor plugin checks: implement health check classes and documentation

Implement remediation-aware health checks across all Doctor plugin modules
(Agent, Attestor, Auth, BinaryAnalysis, Compliance, Crypto, Environment,
EvidenceLocker, Notify, Observability, Operations, Policy, Postgres, Release,
Scanner, Storage, Vex) and their backing library counterparts (AI, Attestation,
Authority, Core, Cryptography, Database, Docker, Integration, Notify,
Observability, Security, ServiceGraph, Sources, Verification).

Each check now emits structured remediation metadata (severity, category,
runbook links, and fix suggestions) consumed by the Doctor dashboard
remediation panel.

Also adds:
- docs/doctor/articles/ knowledge base for check explanations
- Advisory AI search seed and allowlist updates for doctor content
- Sprint plan for doctor checks documentation

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-27 12:28:00 +02:00

2.3 KiB

Raw Blame History

checkId, plugin, severity, tags

checkId

plugin

severity

SMTP Email Connectivity

What It Checks

Reads the SMTP host from Smtp:Host, Email:Smtp:Host, or Notify:Email:Host and the port from the corresponding :Port key (defaulting to 587). Opens a raw TCP connection to the SMTP server with a 5-second timeout. The check passes if the TCP connection succeeds, fails on timeout, socket error, DNS failure, or connection refusal.

Why It Matters

Email notifications deliver approval requests, security alerts, deployment summaries, and audit reports to operators who may not be monitoring Slack or the web UI. If the SMTP server is unreachable, these notifications silently fail. For organizations with compliance requirements, email delivery may be the mandated audit notification channel.

Common Causes

SMTP server is not running or is being restarted
Firewall blocking SMTP port (25, 465, or 587)
DNS resolution failure for the SMTP hostname
Network unreachable between Stella Ops and the mail server
Incorrect host or port in configuration
ISP/cloud provider blocking outbound SMTP

How to Fix

Docker Compose

# Check SMTP configuration
grep 'SMTP__\|EMAIL__SMTP\|NOTIFY__EMAIL' .env

# Test TCP connectivity
docker compose exec gateway bash -c \
  "echo > /dev/tcp/smtp.example.com/587 && echo OK || echo FAIL"

# Update SMTP settings
echo 'Smtp__Host=smtp.example.com' >> .env
echo 'Smtp__Port=587' >> .env
echo 'Smtp__UseSsl=true' >> .env
docker compose restart platform

Bare Metal / systemd

# Verify configuration
cat /etc/stellaops/appsettings.Production.json | jq '.Smtp'

# Test connectivity
telnet smtp.example.com 587
# or
nslookup smtp.example.com

# Update configuration
sudo nano /etc/stellaops/appsettings.Production.json
sudo systemctl restart stellaops-platform

Kubernetes / Helm

# values.yaml
smtp:
  host: smtp.example.com
  port: 587
  useSsl: true
  existingSecret: stellaops-smtp-creds   # Secret with username/password

helm upgrade stellaops ./chart -f values.yaml

Verification

stella doctor run --check check.integration.smtp

check.integration.slack -- Slack notifications (alternative channel)
check.integration.teams -- Teams notifications (alternative channel)

2.3 KiB Raw Blame History