Servers

Logs

Read and search a server's systemd journal live through its agent, and find where service, website, app and cron logs are kept.

Last updated

Monitoring > Logs reads a server's logs from the systemd journal, live, through its agent. Nothing is copied to or stored on the panel: each read asks the agent for the newest lines.

Read a server's logs

Pick an online server at the top of the page, then a source:

SourceWhat it holds
System journalEverything the server logs
KernelKernel messages (dmesg)
Sign-ins and sudoSSH logins, sudo and other authentication
CronWhat the cron daemon started

Then narrow the result:

FilterOptions
Find textPlain text, up to 200 characters, matched without regard to case over the newest 20,000 lines
LevelA journal priority and everything more severe (Emergency, Alert, Critical, Error, Warning, Notice, Info), or All levels
Time rangeAny time, or the last 15 minutes, hour, 6 hours, 24 hours or 7 days
Lines100, 300, 1000 or 2000

Click Read, or tick Refresh every 10 s to follow the log. With a search, the result says how many lines matched out of how many were scanned. Lines that look like errors or warnings are colored; that is a hint, not a filter.

Reading server logs needs servers.logs (owners and admins by default) and agent 0.5.0 or newer.

Other logs

LogWhere
A service's journalThe server's Services tab, Logs on each service. See Servers.
A website's NGINX access and error logsThe website's Logs tab
An app's output and errorsThe app's Logs tab
A cron job's outputAutomation > Cron Jobs, kept with each run
What a job did on a serverThe job's page, from Monitoring > Jobs
What people did in the panelThe audit log