How to enable requests logging?

[msurdi]

I wonder if when starting a service in production (with next start, not with a custom server) there is any way to have in stdout a log of all http requests the server is handling. Even if those requests are serving pre-built static pages and/or SSR pages.

I'm talking about logging the usual:

info: 127.0.0.1 - - [10/Mar/2021:14:02:25 +0000] "GET /something HTTP/1.1" 404 150 "-" "curl/7.64.1"

thanks!

[andrewfritz86]

IMO this is something that deserves a better explanation in the docs, in that I don't think Next exactly supports this out of the box.
We have been using middleware to handle this.

// middleware.js

import { NextResponse } from 'next/server';

export async function middleware({ nextUrl, cookies }) {
  const response = NextResponse.next();
  console.log(JSON.stringify(nextUrl));
  return response;
}

We have been pulling individual keys off the request object and stringifying them, since the whole object doesn't seem to serialize properly.

[seitbekir]

What if I need restricted middleware for bunch of urls, but also I need logging.

[tomups]

You can patch the Next.js server to have full access to the request and response objects, and log them with pino-http for example:

https://www.tomups.com/posts/log-nextjs-request-response-as-json/

[sergiotapia]

this has to be a joke right, nextjs can't NOT have logging??? I'm coming from elixir and i feel like i'm losing my mind.

[realtebo]

Same question here

We are developing a 3rd party integration. So it's fundamental to have full log of method, url with query parameters, headers and body.

[tybro0103]

Simply unbelievable.

Honest question - is OpenTelemetry supposed to be the answer?

[tomups]

I could not find a way to log request / response body with OpenTelemetry, so I think for now patching is still the only way if you need that :(

[ogelami]

I decided to take a stab at it pull request here #74438, logging is optional and initiated with next start --access-log path/file.log