Everything your containers write (application, web server, database) is collected on the machine they run on. There is nothing to configure.
Reading your logs
From a terminal. The command line reads them straight from the machine, over your own SSH key:
# The last 100 lines, then every new line as it is written
vallic logs production --follow
# The requests of the last hour
vallic logs production --since 1h --source proxy
# A window, into a file
vallic logs production --since 2026-11-13T10:00 --until 2026-11-13T10:30 --output incident.log.gz
--since and --until take how long ago (15m, 2h, 3d) or a moment in
UTC. --source narrows it to one kind, and can be given more than once:
| Source | What it is |
|---|---|
container |
What your containers print: PHP-FPM and PHP errors, a Node or Go process, the web server, the database, workers. |
cron |
The output of your scheduled jobs. |
app |
The files your application writes to /var/log/app. |
proxy |
The requests served for your hostnames: status, path, how long it took. |
proxy-error |
The web server's own log: certificates, and what it could not do. On a machine that is your team's own. |
An environment on several machines is read on all of them, each line named
for its machine; --machine web-2 reads one. It takes an SSH key
on your account and the role a shell takes: Developer or above, Admin or above
on production.
From the console. The environment's Logs tab collects the last hour, 6 hours, day or 7 days into a file from each machine, usually within a minute. A file is kept for a day. This takes the Developer role or above, on production too.
You only ever see your own environment's lines. They are read on the machine and handed to you; Vallic Cloud keeps no copy of them anywhere else.
Logging from your own code
A container has no syslog daemon: a site that logs through Drupal's core syslog module logs to nowhere.
Write files instead. Every application container has a directory at
/var/log/app, also in the environment as VALLIC_LOG_DIR. Anything you
write there is kept on the machine, and forwarded if you have set up a
destination.
For Drupal, the Monolog module with a rotating file handler:
// settings.php — or the monolog settings the module reads.
$settings['monolog.channel_handlers']['default'] = ['rotating_file'];
$settings['monolog.handlers']['rotating_file'] = [
'type' => 'rotating_file',
'path' => ($_ENV['VALLIC_LOG_DIR'] ?? '/var/log/app') . '/drupal.log',
'max_files' => 7,
];
For Laravel, point the daily channel at the same directory; the
Laravel page has a worked example. Laravel's default
log path is inside the release, so it starts again on every deploy.
You can read and clear /var/log/app yourself from the environment shell,
and vallic logs --source app follows what is written there.
There is a limit: a tenth of the storage your environment is assigned, between 100 MB and 20 GB. Past it we remove the oldest files first, and never the one being written.
It does not count towards the storage you are assigned.
Set your logger to rotate and you will never meet the limit. To keep more, forward a copy somewhere that keeps it.
What is kept, and for how long
Seven days, on the machine. Logs survive a container restart, and you need
no third-party account to read them: vallic logs and the Logs tab read
those seven days. Anything older is removed.
If you need longer than a week, send a copy somewhere that keeps it, as described below.
The access log
The web server in front of your site always writes an access log.
| Setting | What each line holds |
|---|---|
| Default | Which site, which path, the status, how long it took, when. No visitor address, no query string, no user agent: nothing that is somebody's personal data. |
| Full access logging | The full line, visitor addresses included. |
The full line is written only when full access logging is switched on for the project. It is never written on a machine shared with other teams. Turning it on makes you the controller of that data.
Sending a copy somewhere else
Forwarding is an add-on per project, included at no cost. It appears on the project's invoice, at nothing, as soon as the project sends its logs somewhere.
- Add the collector once, under your team's settings, in Integrations: Datadog, New Relic, Logz.io, Axiom, Grafana Loki, Splunk, an OpenTelemetry collector, a plain syslog endpoint, or an S3-compatible bucket to archive them in. Give it a name, whatever that service needs to identify your account, and the token. The token is encrypted and never shown again.
- Choose it as the destination on the project's configuration page.
Both steps take the Admin role or above. Any project on the team can point at the same integration, and rotating the token in one place fixes all of them.
Forwarding is not offered on the entry line of machines; a larger machine adds it. Logs are still kept on the machine either way.
A plain syslog endpoint is still a destination. Host, port, protocol, no token. TCP unless the endpoint insists otherwise: UDP drops messages silently under load.
Forwarding is additive: the machine keeps its own copy. Shipping is done by Vector on the machine.
What is sent, and what is not
Only your project's containers. Never another customer's, and never the machine's own output.
The access log is sent with them where the machine is your team's own. On a machine shared with other teams it is not: that log is the machine's, and holds every site's requests.
If the endpoint is unreachable, messages queue on disk and are delivered when it comes back.
Changes take effect on the next reconcile
Saving a destination sends it to every machine the project runs on, which picks it up within about a minute.
Next
- Backups: the other thing that leaves the machine.
- Monitoring: metrics and availability.
- Shell access: reading what is on the machine yourself.
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console