Skip to Content

www logs one JSON line per event, and unknown pages return 404

Shipped 2026-10-28

www logged coloured text, so Datadog saw every line as info, split each stack trace into one event per frame, and dropped the error passed to most logger.error calls. It now uses the API’s log format: one JSON line per call with a real level, an event field, and the error’s stack in the same line. Every request writes an http.request line with the API’s field names (query string dropped), and an Express error handler logs http.unhandled_error and serves the 500 page that was never wired up; malformed JSON and bad URL encodings keep their 400 and log at warn. Per-request detail such as redis.get_json moves to debug; an expired session cookie is a warn, not an error.

Unknown URLs rendered the 404 page with status 200; they now return 404, as does a member directory page for a member that doesn’t exist. The directory’s contact page for an unknown member asked for a view that doesn’t exist and answered 500; it now returns the 404 page.

The www monitors (5xx, social sign-in failures) follow once these logs have run in production. The shared format is documented in Infra: Logging.

Last updated on