review-logging-patterns

Replace scattered console.log calls with a request-scoped wide event using evlog's useLogger() and log.set() to accumulate context, emitted once per request. The Skill provides before/after transformation examples for single logs, multiple related logs, and full request lifecycles.

For Nuxt, add the evlog/nuxt module and use auto-imported useLogger(event) in handlers. For Next.js, create a central config with createEvlog() from evlog/next and wrap route handlers with withEvlog(). The @evlog/cli init command can automate setup on both.

Yes, evlog provides dedicated middleware for Express, Hono, Fastify, Elysia, NestJS, React Router, oRPC, SvelteKit, Astro, Cloudflare Workers, and AWS Lambda. Each integration exposes a request-scoped logger via useLogger() or the framework's context object.

A wide event is a single comprehensive log entry capturing all context for one logical operation, such as user, cart, payment, and error data for a request. It replaces many scattered log lines, making incident debugging faster since everything is in one structured event.

evlog includes drain adapters for Axiom, OTLP, HyperDX, PostHog, Sentry, Better Stack, Datadog, Loki, and ClickHouse, configured via environment variables. Wrap the adapter in createDrainPipeline for batching, retry with backoff, and buffer overflow protection in production.

Avoid wide events for granular operations like individual database queries or cache hits; include those as context in the parent request's wide event instead. Also never log sensitive data such as passwords, tokens, or full card numbers in any event.