sneak b09d23fa0d server: report HTTP handler panics to Sentry (closes #107) ...

DNSWATCHER_SENTRY_DSN was read but never used. This ports the Sentry
integration from gohttpserver with sentry-go v0.49.0. The server's start
hook calls sentry.Init when the DSN is set; a DSN Sentry cannot parse
fails the hook, so startup stops with the parse error. sentryhttp, with
Repanic, reports handler panics and passes them on to chi's Recoverer.
Shutdown sends queued reports once the HTTP server has stopped. The
client uses the older transport (DisableTelemetryBuffer): with the
default one, Flush can return before sending a report made just before
it. The DSN is checked at server start, not in config, so the config
test is unchanged. sentry-go raises several golang.org/x modules.

Model: opus-5-5

2026-10-01 20:24:28 +00:00

..

export_test.go

server: report HTTP handler panics to Sentry (closes #107)

2026-10-01 20:24:28 +00:00

routes_test.go

metrics: rate limit /metrics per client address before Basic Auth (closes #101)

2026-10-01 22:09:14 +02:00

routes.go

server: report HTTP handler panics to Sentry (closes #107)

2026-10-01 20:24:28 +00:00

sentry_test.go

server: report HTTP handler panics to Sentry (closes #107)

2026-10-01 20:24:28 +00:00

server_test.go

server: report HTTP handler panics to Sentry (closes #107)

2026-10-01 20:24:28 +00:00

server.go

server: report HTTP handler panics to Sentry (closes #107)

2026-10-01 20:24:28 +00:00