Skip to main content

Server log

Monitoring → Server log searches what the server has written: the framework, the applications and the libraries they use, whatever started the server. The log is kept on disk, in files rotated by size — 10 MB per file, the five previous files kept —, so it survives a restart. Only superusers see the Monitoring page.

At a glance​

MonitoringLiveServer logRetention⌕ Search a message, a logger, an error, a request id…WARNING and above ▾Any module ▾Last 24 hours ▾ExportDownload files184 entries (from 52,310 lines) · liberty.log 4.1 MBERROR10:42:11liberty.jobsstep 'load' failed: period 2026-02 is closed[a91f03c2]WARNING10:40:02liberty.connectors.sqlslow query sales_get (8.2 s)[5be2d0e1]WARNING09:58:37nomasx1.securityuser JDOE has no address book entryINFO09:00:00liberty.jobsnightly_sync succeeded in 72 sLog levels per moduleApplied at once and saved (●). Inherit = the parent module's level.liberty.jobs ●INFO ▾nomasx1 ●DEBUG ▾Three tabslive, server log, retentionSearchlevel, module, periodClick a lineopens its exceptionExport, downloadthe matches, the filesRequest idclick: that request onlyLevels per moduleapplied at once
ControlEffect
SearchText in the message, the module, the exception or the request id.
LevelAny level, or a floor: WARNING and above keeps the warnings, the errors and the critical messages.
Any moduleOne module and its sub-modules — liberty.jobs, nomasx1. A name can be typed.
PeriodLast hour, Last 24 hours (the default), Last 7 days, Everything kept.
ReloadReads the files again.

The filters are kept in the browser. The page shows the 500 newest matches — N entries (from M lines), with the files read and their size —; when there are more, it says so: narrow the search.

A click on a line opens it: the full message and its exception. The request id in brackets after a message — the one an error page shows the user — keeps that request only: every line written while serving it.

The same message written many times in a row is kept once, followed by (previous message repeated N times).

Export and download​

ButtonGives
ExportThe matching entries as a text file, oldest first — up to 100,000.
Download filesThe log files themselves, current and previous, in a ZIP.

Log levels per module​

The card at the bottom sets how much each module writes. Pick a level for a module — Inherit takes its parent's —, or add a module by name. A change applies at once, without a restart, and is kept for the next start (● marks a module set this way). Raise a module to DEBUG while investigating, then set it back: a verbose module fills the files quickly.