Monitoring & Logs
Monitor your deployments in real-time with detailed logs for the build process, deployment, and application runtime.
Deployment Overview
In your dashboard, you can see:
- Deployment status (pending, building, deploying, running, failed)
- Deployment history with timestamps
- Git commit hash and deployed branch
This information helps you understand the progress and status of each deployment.
Build Logs
Build logs display the complete output from the build process, whether from your Dockerfile or build command.
Use build logs for debugging:
- Dockerfile syntax errors
- Dependency installation failures
- Build script errors
- Environment variable issues
Build logs are available for 7 days after deployment.
Runtime Logs
Runtime logs are the stdout and stderr output from your running application.
Use runtime logs to:
- Monitor application behavior
- Debug runtime errors
- Track important events (logins, transactions, errors)
- Check application health status
Runtime logs are available in your dashboard and stored for 7 days. If you need longer retention, you can integrate with an external logging service.
Web App Health
Pay-as-you-go web apps don't have runtime logs yet. Their project page shows Web app health instead, for the last 24 hours:
- How many requests the app answered, and how many failed
- Which pages failed, how many times, and when it last happened
- How each one failed: timed out, ran out of memory, crashed, not responding, cut off, or a server error from the app's own code
It's updated every 5 minutes, so a failure in the last few minutes may not show yet. Error messages aren't included. The AI in your workspace sees the same summary, so you can ask it to fix a failing page.
How to View Logs
To view logs from a deployment:
- Go to your project dashboard
- Select a deployment from the history
- Click on that deployment
- Scroll to the Logs section
- Select the Build Logs or Runtime Logs tab
Usage Metrics
In the Usage tab, you can see usage metrics:
- Requests — Total requests this month
- Data Transfer — Total data sent out
- Compute Hours — Total compute hours used (only counted when handling traffic)
- Storage — Total storage used
This data helps you monitor your usage against your plan quotas.
Alerts & Notifications
Currently, the system sends notifications for:
- Deployment complete (successful or failed)
- Build failed
Notifications are sent to the email address associated with your GitHub account.
Monitoring Best Practices
- Check logs after each deployment to ensure your application is running normally
- Use external monitoring services like DataDog, New Relic, or Grafana for advanced observability
- Make sure you're logging important events like authentication and application errors
- Check your usage dashboard regularly, so your sites don't pause when their traffic allowance runs out
Troubleshooting with Logs
- Build failed → Check build logs to see errors in your Dockerfile or build script
- Application crashes after running → Check runtime logs for exceptions or errors