Node.js APM Now Supports Next.js 16 and Express 5

You can now see which Next.js 16 routes are slow or failing, and keep monitoring your Express apps when you move to Express 5. The Atatus Node.js APM agent adds Next.js 16 App Router support in version 3.5.3 and Express v5 support in version 3.5.2.

Earlier agent versions reported App Router requests under names like GET unknown route. Pages and route handlers are now named by the route they matched, such as GET /products/[id]. Update the agent to 3.5.3 or later. The Next.js setup docs cover installation.

What's new in the Node.js agent

• Named App Router routes: Next.js 16 pages and route handlers each appear under their matched route, so their traffic is no longer lumped into one unknown route.
• Express 5: Agent 3.5.2 adds support for Express v5, so you can upgrade Express without losing monitoring.
• No hang with body capture: Requests no longer hang when response body capture (logBody or captureBody) is on and a streamed response waits for a drain event.
• ESM fixes: MongoDB and kafkajs calls are now instrumented in ESM apps on Node.js 20 and later that import MongoClient or Kafka directly.
• Simple Next.js setup: Install atatus-nodejs, start Next.js with NODE_OPTIONS='-r atatus-nodejs/start-next.js', and set your license key and app name.