Why logging matters in production in Express

Introduction

Logging helps you see what your app is doing when users use it. It shows errors and important events so you can fix problems fast.

When your app crashes and you want to know why.

When you want to track user actions for security or analysis.

When you need to monitor app performance and spot slow parts.

When debugging issues that happen only in real user environments.

When auditing changes or access to sensitive data.

Syntax

Express

app.use((req, res, next) => {
  console.log(`${req.method} ${req.url}`);
  next();
});

This example logs every request method and URL to the console.

Use middleware in Express to add logging for all requests.

Examples

Simple message logged when the server starts.

Express

console.log('Server started on port 3000');

Logs each incoming request's method and URL.

Express

app.use((req, res, next) => {
  console.log(`Request: ${req.method} ${req.url}`);
  next();
});

Logs errors that happen during request handling.

Express

app.use((err, req, res, next) => {
  console.error('Error:', err.message);
  res.status(500).send('Something broke!');
});

Sample Program

This Express app logs every request's method and URL, then responds with 'Hello World!'. It also logs when the server starts.

Express

const express = require('express');
const app = express();

// Log every request method and URL
app.use((req, res, next) => {
  console.log(`${req.method} ${req.url}`);
  next();
});

app.get('/', (req, res) => {
  res.send('Hello World!');
});

app.listen(3000, () => {
  console.log('Server started on port 3000');
});

Important Notes

Logging too much can slow your app and fill disk space quickly.

Use different log levels (info, error) to organize logs better.

Consider using logging libraries like Winston or Morgan for more features.

Summary

Logging shows what happens inside your app in real time.

It helps find and fix problems faster in production.

Good logging practices improve app reliability and user trust.