The Monitoring page
Liberty Next → Operate → Monitoring opens a live view of the server. It is shown to superusers only and refreshes itself through the live connection (Socket.IO). Its three views are picked from a row of cards at the top — an icon, the name and one line on what the view is for. This page describes the first, Live; the other two are Server log and Retention.
At a glance
The four KPIs
| KPI | Meaning |
|---|---|
| Connected users | Live sessions — one per open browser tab connected to the server. |
| Active locks | Records currently open for editing. |
| Pools | Pools opened / pools configured. A pool opens on its first use. |
| Uptime | Time since the server started. |
Database pools
One row per pool: Pool, Dialect, In use (connections busy), Idle (open and free), Overflow (connections beyond the pool's size). not opened means no query has used the pool yet.
All connections In use with Overflow above 0 means queries wait for a connection: look for slow queries in the log, or raise the pool's size in Liberty Next → Administer → Pools.
Runtime
The server's version and platform, the numbers of connectors and screens, the AI assistant's state, the licence and the Socket.IO clients.
Connected users
One row per session: User, Session, Client (address). A user with three tabs open has three rows.
Record locks
When a record is opened for editing, it is locked so that two people do not overwrite each other: Record, User, Since (time). The lock is released when the dialog closes or the user's session ends.
Live log tail
The latest lines of the server log, newest at the bottom.
| Control | Effect |
|---|---|
| All / INFO+ / WARN+ / ERROR | Minimum level shown. |
| Filter… | Text in the logger name or the message — an error_id, a request id, a connector. Clear filter empties it. |
| Pause / Resume | Stops the scrolling to read; new lines keep arriving. |
Errors are red, warnings orange, debug lines dimmed; a line with a stack trace can be unfolded (traceback). For older lines, search the Server log tab.