Operations

Logs

Read the systemd journal and container output from any server.

Read logs from any server without SSH: the systemd journal, a single service, or any container, including apps and databases.

Sources

Source	Reads
Journal	All units, or one unit such as nginx.service, read as JSON so every line keeps its unit and priority.
Container	A container's stdout and stderr, merged by timestamp.
Application	The current release of an app, with its state and restart count: container output, the public service of a Compose app, or the journal of a systemd app.

Searching logs

Logs → Search all apps' logs finds lines containing some text (any case) in every app's logs, or one app's, over the last hour, day or week. Each server searches what it still has (Docker keeps the last 30 MB of each app's output; the journal keeps systemd apps' logs), so nothing is copied off your servers. Secrets are masked in the results.

Following

Follow mode polls for new lines. The journal is followed with its cursor and containers with a timestamp, so no line is skipped or shown twice.

Limits

Up to 1,000 lines per read; the newest lines are kept when output is large.
Very long lines are truncated at 2,000 characters.
Reads are jobs whose output is encrypted at rest and deleted after an hour.
Opening a log is audited once per session, not on every poll.

On the server

VPSPilot’s own services log to the journal:

bash

journalctl -u vpspilot-agent -fjournalctl -u vpspilot-helper -f