Monitoring — overview
How to watch a running Liberty Next server: the Monitoring page for superusers (sessions, record locks, database pools, runtime, live log), the health endpoints for probes, and the command-line status and doctor.
The Monitoring page
Block by block, the Liberty Next Monitoring page: the four KPIs, database pools, runtime, connected users, record locks and the live log tail — what each value means and when to act.
Server log
Monitoring → Server log in Liberty Next: the server log kept on disk and rotated by size, searched by level, module, text and period, an exception opened, one request followed, the matches exported, the files downloaded, and the log level of each module changed at once.
Retention
Monitoring → Retention in Liberty Next: every store the server keeps growing — job runs, job files, notifications, configuration versions, change packages, saved views, the server log — with its policy, its size, a dry-run Preview and Run now.
Health endpoints
Liberty Next health endpoints: /health (liveness), /ready (readiness — the framework database answers) and /info (version and counts, more details when signed in), with examples for Docker, Kubernetes and external probes.