All 15 Express & Middleware questions
More in Express & Middleware
What is CORS middleware in Express, and how does the cors package simplify configuring Cross-Origin Resource Sharing? What is the difference between res.send(), res.json(), and res.end() in Express, and when should each be used? How do you write custom Express middleware that needs to perform asynchronous work, like checking a value against a database, before calling next()? How would you implement request validation middleware in Express using a schema-validation library like Zod or Joi? How would you structure a large Express application using the Router to organize routes into feature-based or resource-based modules? How would you implement conditional middleware in Express that only applies to certain requests based on a runtime condition? How would you implement a middleware that adds a correlation/request ID to every incoming request for tracing purposes across a distributed system? How would you implement a global request timeout middleware in Express to prevent a slow request from hanging indefinitely?
Advertisement
Back to results for “Monitoring”
Node.js › Express & Middleware

How would you implement a request-logging middleware in Express that captures method, path, status code, and response time for every request?

Advanced

Answer

A logging middleware records the request's start time when it first runs, then attaches a listener to the response's 'finish' event (fired once the response has been fully sent) to calculate the elapsed duration and log the complete request/response summary -- this pattern, rather than logging synchronously right after calling next(), is necessary because next() returns before the response is actually sent, so the status code and true total duration aren't known until the response actually finishes.
app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    const duration = Date.now() - start;
    console.log(`${req.method} ${req.path} ${res.statusCode} ${duration}ms`);
  });
  next();
});
Real-world example An API's custom logging middleware records every request's method, path, final status code, and total response time by listening for the response's 'finish' event, giving operations visibility into which endpoints are slow or frequently erroring without needing a third-party logging library.

Common follow-ups: Why does logging immediately after calling next() give an incorrect status code and duration compared to listening for 'finish'?;How does this hand-rolled approach compare to using a mature middleware like morgan for the same purpose?

Logging & Monitoring;Performance Optimization & Profiling
All 15 Express & Middleware questions