feat: implement watcher monitoring orchestrator #2

New Issue

clawbot · 2026-02-19T22:42:28+01:00

clawbot commented

2026-02-19 22:42:28 +01:00

Implement the full monitoring loop in internal/watcher/watcher.go:

On startup: immediately run all checks
Periodic scheduling: DNS+port every config.DNSInterval, TLS every config.TLSInterval
Domain check: LookupNS → compare with state → notify on NS changes
Hostname check: LookupAllRecords per NS → compare per-NS → detect changes
Port check: collect IPs → check ports 80, 443 → detect state changes
TLS check: for open 443 ports → check cert → detect changes/expiry
State persistence after each cycle
First run: baseline only, no notifications
Graceful shutdown

Define interfaces for dependencies (DNSResolver, PortChecker, TLSChecker, Notifier) to enable testing with mocks.

Implement the full monitoring loop in `internal/watcher/watcher.go`: 1. On startup: immediately run all checks 2. Periodic scheduling: DNS+port every config.DNSInterval, TLS every config.TLSInterval 3. Domain check: LookupNS → compare with state → notify on NS changes 4. Hostname check: LookupAllRecords per NS → compare per-NS → detect changes 5. Port check: collect IPs → check ports 80, 443 → detect state changes 6. TLS check: for open 443 ports → check cert → detect changes/expiry 7. State persistence after each cycle 8. First run: baseline only, no notifications 9. Graceful shutdown Define interfaces for dependencies (DNSResolver, PortChecker, TLSChecker, Notifier) to enable testing with mocks.

sneak was assigned by clawbot

2026-02-19 22:42:28 +01:00

clawbot referenced this issue from a commit

2026-02-19 22:48:52 +01:00

feat: implement watcher monitoring orchestrator

clawbot referenced a pull request that will close this issue

2026-02-19 22:49:06 +01:00

feat: implement watcher monitoring orchestrator (closes #2) #8

sneak closed this issue

2026-02-20 09:06:42 +01:00

sneak referenced this issue from a commit

2026-02-20 09:06:44 +01:00