Logs & metrics

Follow build logs

Open a deployment in the dashboard to inspect checkout, installation, and build output. For a failed build, start with the first error and the command that produced it.

From the terminal, use the deployment UUID:

arvumi logs DEPLOYMENT_UUID

This command streams build logs. Application requests and function output appear in runtime logs instead.

Read runtime logs

Open your project and choose Logs. This opens the project’s Grafana Logs Drilldown. Sign in with Arvumi if prompted, select a time range, and choose the relevant service.

Node.js console.log and Python print output are captured automatically. No logging SDK is required. Include useful context such as an operation name or request identifier, and avoid credentials, tokens, or sensitive request bodies.

Understand application metrics

Choose Metrics in the project to view recorded requests, server errors, function calls, and dispatch timing. Choose a time range that covers the activity you want to investigate. Hourly buckets use UTC.

Check coverage and freshness indicators when interpreting the charts. Delayed or uncertain data does not mean zero traffic. Dispatch timing is not a browser’s end-to-end page load time.

A practical debugging path

1. Build failed? Read deployment logs. Check the source commit, root directory, dependency installation, and build output.
2. Site returns 404? Check the served deployment, output directory, and route. Single-page applications need an explicit fallback rewrite.
3. Function fails? Invoke the endpoint, then look at runtime logs. Check its manifest, dependencies, environment allowlist, and resource limits.
4. Database unavailable? Check readiness and environment, allow for a sleeping free cluster to wake, and confirm a redeploy followed configuration changes.
5. No logs visible? Check the project, service, and time range. Send a new request to the function and allow time for logs to arrive.

Log access follows your team

Use your Arvumi account and the project’s Logs action. If access is denied, confirm that you are signed into the right account and still belong to the project’s team. Contact your team owner or admin if you need access.

When you need help

If the issue continues after these checks, contact Arvumi support with the project or deployment UUID, affected URL, error, and timestamp with its time zone. Redact credentials, environment values, and personal information from logs.