Documentation

Logs and observability

See what a build did, what your server printed, and how traffic and the cache are behaving.

Build logs

Every deployment keeps its build log. Open the deployment in the dashboard to watch it stream, or use the CLI:

$ vtx logs a1b2c3

The log ends when the build ends, so following it from the CLI exits with the result. Logs are kept after the deployment finishes.

Runtime logs

For server apps, Runtime Logs in the project shows what your application writes to standard output and standard error: console.log output, errors and stack traces. Choose a deployment to see its output.

$ vtx logs --runtime a1b2c3
$ vtx logs --runtime --tail 500 a1b2c3

By default the last 100 lines are shown and new lines follow. Static sites have no runtime logs, because nothing runs.

Traffic and regions

Observability in the sidebar charts requests across your projects: volume, status codes, and where visitors are. The Countries and regions view maps them. Charts can be filtered by project and time range.

Cache

The Cache view shows how often responses were served from the edge cache instead of your application. A low hit rate on a route you expected to be cached usually means the response is not marked shareable; see Caching.