Metrics, logs and commands

Metrics

One card per server behind the environment, including shared database, cache and search servers.

CPU, network and disk I/O come from the provider's metrics API. Memory, load average and disk usage are sampled live over SSH — the provider does not expose memory, so Nautvia asks the machine directly. If a server is unreachable, that part of the card degrades rather than the page failing.

Periods depend on your plan:

Plan	Periods
Solo	1 hour, 24 hours
Studio	1 hour, 24 hours, 7 days
Agency	1 hour, 24 hours, 7 days

Charts refresh every minute; readings are cached for 30 seconds.

Logs

Six sources, tailed live over SSH from your application server:

Source	File
Magento system	var/log/system.log
Magento exception	var/log/exception.log
Magento debug	var/log/debug.log
nginx access	/var/log/nginx/access.log
nginx error	/var/log/nginx/error.log
PHP-FPM	the pool's log

Choose 200 or 500 lines. Output is cached for five seconds so the page can poll without hammering the server.

Nothing is shipped or stored. There is no log search, no history, and no retention beyond what the operating system's own rotation keeps on your server. When you tear the environment down, its logs go with it.

If you need searchable history, ship logs somewhere yourself — the store is a normal server and you have SSH access.

One-off commands

The Commands tab runs a single command in the live release, as the deploy user, from your store's root:

bin/magento indexer:reindex
bin/magento cache:flush
bin/magento config:set web/seo/use_rewrites 1
bin/magento setup:static-content:deploy -f de_DE

Things to know:

• Fifteen minute timeout. A long reindex will be cut off; run it over SSH instead.
• Output streams back every few seconds; the stored log is capped at the last 64 KB.
• The last 20 commands are listed, with who ran each one and how long it took.
• Commands are refused during a deploy — one would run half against the old release and half against the new.

For something that should happen on every release, use a deploy command instead — see Deploy hooks and commands.

Deployment logs

Each deployment keeps its full output, streamed as it happens. How many deployments stay in the list depends on your plan — 10 on Solo, 50 on Studio, unlimited on Agency.

Log contents are erased after 90 days, and command output after 90 days. The records themselves stay, so your history and rollback targets are intact — it is the output that goes, because a command you ran may have printed customer data. See the Privacy Policy.