sneak 68c3c66061 log: write durations as text, not nanoseconds (closes #228) ...

The JSON log wrote a Go duration as a bare count of nanoseconds, so
the watcher starting line showed dnsInterval 120000000000 for 2m and a
delivery retry showed retryIn 1015437050. Each duration logged is now
passed through its String() form: dnsInterval and tlsInterval when the
watcher starts, retryIn on a delivery retry, and latency on a
succeeded port check. A test checks that retryIn is logged as the
text of the wait the retry actually took.

The request log's latency_ms is left as it is: its key names its
unit.

Model: opus-5-5

2026-10-02 06:35:40 +00:00

..

cancelled_test.go

watcher: save and notify nothing for a cut-short port or TLS check (closes #185)

2026-10-01 22:49:45 +02:00

cname_test.go

watcher: follow a watched name's CNAME for port and TLS checks (closes #203)

2026-10-02 08:26:27 +02:00

export_test.go

watcher: follow a watched name's CNAME for port and TLS checks (closes #203)

2026-10-02 08:26:27 +02:00

inconsistency_test.go

watcher: notify NS query failure and recovery (closes #104)

2026-10-01 22:23:33 +02:00

interfaces.go

watcher: notify NS query failure and recovery (closes #104)

2026-10-01 22:23:33 +02:00

nsaddress_test.go

watcher: notify nameserver address changes (closes #105)

2026-10-01 23:23:26 +02:00

nsfailure_test.go

watcher: keep port state when no nameserver of a name answered (closes #193)

2026-10-02 00:44:49 +02:00

watcher_test.go

watcher: follow a watched name's CNAME for port and TLS checks (closes #203)

2026-10-02 08:26:27 +02:00

watcher.go

log: write durations as text, not nanoseconds (closes #228)

2026-10-02 06:35:40 +00:00