Strapi monitoring comes down to four things: a request log for every call to your content API and admin panel, response times per route (with an eye on populate ), error rates by status class, and a record of who is hammering your public endpoints. Strapi 5 gives you a Winston-based logger and a Koa middleware stack to build this on. This guide sets up Strapi logging with a custom request-log middleware, shows where performance problems usually come from, and covers rate limiting on public content APIs.
Versions: the configuration follows the Strapi 5 documentation as of November 2026 (current release 5.62.0) on Node.js 22. The request-log middleware below was run against a mocked Koa context on Node 22.23; its output is pasted where it appears.
What to monitor in a Strapi 5 app
One Strapi process serves several kinds of caller, and each fails in its own way.
The content API under /api/* : public or token-protected reads from your frontend, apps and anyone else who finds it.…