Deployment logs
Every deployment streams logs in real time as your application builds and starts up. To view logs in the dashboard, navigate to Deployments, select the deployment you want to inspect, and open the Logs tab. You can filter log output by severity level or search for keywords using the toolbar above the log viewer. Varo Cloud surfaces three log levels:- INFO — general operational messages, startup events, and request traces
- WARN — non-fatal conditions that may require attention
- ERROR — failures that need immediate investigation
GET /deployments/{id} endpoint and inspect the status field:
error field contains a short description of the failure reason. Full build output is always available in the Logs tab of the deployment detail page in your dashboard.
Application metrics
Varo Cloud automatically collects the following metrics for every active deployment:- CPU usage — percentage of allocated CPU consumed
- Memory usage — RAM consumed versus the deployment’s memory limit
- Request rate — incoming HTTP requests per second
- Error rate — percentage of requests returning 5xx responses
- Response latency — p50, p95, and p99 response times in milliseconds
Metrics retention depends on your plan: Starter plans retain metrics for 7 days, while Pro and Enterprise plans retain metrics for 30 days. For longer retention and advanced querying, connect your Datadog account via the Integrations settings.
Health checks
Varo Cloud periodically pings your application’s health check endpoint to verify that it is responding correctly. If the endpoint fails to respond within the configured timeout, Varo Cloud marks the deployment as unhealthy and triggers any alert rules you have configured. To configure your health check, go to Project → Settings → Health Check and fill in the following fields:- Health Check URL — the path Varo Cloud should GET, for example
/healthz - Interval — how often to run the check, in seconds (minimum 10 seconds)
- Timeout — how long to wait for a response before treating the check as failed, in seconds
200 OK response to consider the deployment healthy. Any other status code or a connection timeout counts as a failed check.
Alerts
Alerts let you define thresholds on any collected metric and get notified through email or Slack when those thresholds are breached.Configure the alert condition
Choose the metric you want to monitor, set a threshold value, and define the evaluation window — the period over which the metric must exceed the threshold before the alert fires. For example, you might alert when average CPU usage exceeds 80% for a sustained 5-minute window.
High CPU Usage
Metric: CPU usage
Threshold: greater than 80%
Window: 5 minutes
Fires when sustained compute pressure risks degrading response times or triggering an out-of-memory condition.
Threshold: greater than 80%
Window: 5 minutes
Fires when sustained compute pressure risks degrading response times or triggering an out-of-memory condition.
Elevated Error Rate
Metric: Error rate
Threshold: greater than 1%
Window: 2 minutes
Fires when a meaningful percentage of requests are returning errors, signalling a likely regression in a recent deployment.
Threshold: greater than 1%
Window: 2 minutes
Fires when a meaningful percentage of requests are returning errors, signalling a likely regression in a recent deployment.
