Performance monitoring basics in Express - Step-by-Step Execution

Concept Flow - Performance monitoring basics

Start Application

↓

Collect Metrics

↓

Analyze Metrics

↓

Detect Performance Issues

↓

Alert or Log

↓

Optimize Application

↩Back to Collect Metrics

This flow shows how performance monitoring collects data, analyzes it, detects issues, alerts, and helps optimize the app continuously.

Execution Sample

Express

const express = require('express');
const app = express();
app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    console.log(`Request took ${Date.now() - start} ms`);
  });
  next();
});

This code measures how long each HTTP request takes and logs the duration.

Execution Table

Step	Action	Timestamp Start (ms)	Timestamp End (ms)	Duration (ms)	Output
1	Request received	1000
2	Middleware start timer	1000
3	Request processing	1000
4	Response finish event triggered		1025	25	Request took 25 ms
5	Log output				Request took 25 ms
6	Next middleware or route handler

💡 Request processing finished, duration logged, middleware passed control forward

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
start	undefined	1000	1000	1000
Duration	undefined	undefined	25	25

Key Moments - 2 Insights

Why do we use 'res.on("finish")' instead of logging immediately after 'Date.now() - start'?

Because the response finishes asynchronously, logging inside 'res.on("finish")' ensures we measure the full request time, as shown in execution_table step 4.

What does 'next()' do in the middleware?

'next()' passes control to the next middleware or route handler, allowing the request to continue processing, as seen in execution_table step 6.

Visual Quiz - 3 Questions

Look at the execution table, what is the duration of the request at step 4?

A 25 ms

B 1000 ms

C 1025 ms

D 0 ms

💡 Hint

Check the 'Duration (ms)' column at step 4 in the execution_table.

At which step does the middleware start the timer?

A Step 1

B Step 4

C Step 2

D Step 6

💡 Hint

Look at the 'Action' column in execution_table for when the timer starts.

If we remove 'next()', what happens to the request flow?

A Duration logs twice

B Request processing stops after middleware

C Request continues normally

D Response never finishes

💡 Hint

Refer to key_moments about the role of 'next()' and execution_table step 6.

Concept Snapshot

Performance monitoring basics in Express:
- Use middleware to measure request time
- Start timer at request start
- Use 'res.on("finish")' to detect response end
- Log or send metrics for analysis
- Use 'next()' to continue request flow

Full Transcript

Performance monitoring in Express involves adding middleware that records the time when a request starts and listens for the response to finish. When the response finishes, it calculates the total time taken and logs it. This helps detect slow requests. The middleware uses 'next()' to pass control to the next handler so the request can be processed fully. This cycle repeats for every request, enabling continuous monitoring and optimization.