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.
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:
| Source | What it holds |
|---|---|
| System journal | Everything the server logs |
| Kernel | Kernel messages (dmesg) |
| Sign-ins and sudo | SSH logins, sudo and other authentication |
| Cron | What the cron daemon started |
Then narrow the result:
| Filter | Options |
|---|---|
| Find text | Plain text, up to 200 characters, matched without regard to case over the newest 20,000 lines |
| Level | A journal priority and everything more severe (Emergency, Alert, Critical, Error, Warning, Notice, Info), or All levels |
| Time range | Any time, or the last 15 minutes, hour, 6 hours, 24 hours or 7 days |
| Lines | 100, 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
| Log | Where |
|---|---|
| A service's journal | The server's Services tab, Logs on each service. See Servers. |
| A website's NGINX access and error logs | The website's Logs tab |
| An app's output and errors | The app's Logs tab |
| A cron job's output | Automation > Cron Jobs, kept with each run |
| What a job did on a server | The job's page, from Monitoring > Jobs |
| What people did in the panel | The audit log |