Path                      Requests    % of Total
/                        15,234      45.2%
/api/users               8,421       25.0%
/dashboard               4,892       14.5%
/api/posts               3,128       9.3%
Other                    2,000       6.0%

Use this data to:

Identify popular pages
Optimize frequently accessed routes
Cache high-traffic endpoints
Plan infrastructure scaling

Real-Time Logs

Terminal Logs

Build and deployment logs from your application:

Access: Project → Logs → Terminal tab

Features:

Real-time streaming during builds
Historical build logs
Color-coded output
Copy/download logs
Search and filter

What you'll see:

[INFO] Installing dependencies...
[INFO] Running build command...
[INFO] Build completed successfully
[INFO] Starting application on port 3000
[SUCCESS] Deployment complete!

Server Logs

Runtime logs from your deployed application:

Access: Project → Logs → Server tab

Each log entry includes:

Timestamp: When the request occurred
IP Address: Client's IP address
HTTP Method: GET, POST, PUT, DELETE, etc.
Path: Requested URL path
Status Code: HTTP response code (200, 404, 500, etc.)
Response Time: Time taken to process the request (ms)

Example:

2025-01-15 14:32:18 - 192.168.1.1 - GET /api/users - 200 - 45ms
2025-01-15 14:32:19 - 192.168.1.2 - POST /api/auth - 201 - 120ms
2025-01-15 14:32:20 - 192.168.1.1 - GET /dashboard - 200 - 32ms

Log Actions

Available for both Terminal and Server logs:

Copy Logs - Copy all logs to clipboard for sharing or analysis
Download Logs - Download logs as .txt file for long-term storage
Clear Logs - Clear the current log view (doesn't delete historical data)

Performance Monitoring

Response Times

Track how fast your application responds:

Average Response Time: Overall mean response time
Per-Route Performance: Response time by endpoint
Time-series Analysis: Performance trends over time

⚠️ Warning: Response times over 500ms may indicate performance issues. Consider:

Database query optimization

Caching strategies

Code optimization

Infrastructure scaling

Status Code Distribution

Monitor application health by tracking HTTP status codes:

2xx Success: Successful requests
3xx Redirects: Redirect responses
4xx Client Errors: User errors (404, 400, etc.)
5xx Server Errors: Application errors (500, 503, etc.)

High rates of 4xx or 5xx codes may indicate:

Broken links (404)
Invalid requests (400)
Server crashes (500)
Resource exhaustion (503)

Resource Usage

Current Status

View real-time deployment status:

Status: Running, Building, Failed, Stopped
Uptime: How long the deployment has been active
Last Deployed: When the current version was deployed
Build Duration: How long the last build took

Deployment History

Track all previous deployments:

Build Status - Success, Failed, or Canceled for each deployment
Commit Info - Git commit hash and message for each deploy
Duration - Build and deploy time for performance tracking
Screenshots - Visual snapshots of deployed application

Alerts & Notifications

Build Notifications

Get notified when:

Build completes successfully
Build fails
⚠️ Build warnings occur
🚀 Deployment goes live

Performance Alerts (Coming Soon)

Automatic alerts for:

High error rates (>5% 5xx errors)
Slow response times (>1s average)
Traffic spikes (>200% increase)
Downtime detection

Best Practices

1. Monitor Regularly

Check your analytics dashboard:

Daily for active projects
Weekly for stable deployments
After major releases

2. Set Performance Baselines

Establish normal metrics:

Typical response time
Expected traffic patterns
Normal error rates

3. Investigate Anomalies

When you see unusual patterns:

Check server logs for errors
Review recent code changes
Verify external service status
Scale resources if needed

4. Use Logs Effectively

Terminal Logs:

Debug build failures
Verify dependency installation
Check build output

Server Logs:

Track user behavior
Identify slow endpoints
Debug runtime errors
Monitor API usage

5. Optimize Based on Data

Use analytics to:

Cache popular routes
Optimize slow endpoints
Add rate limiting to high-traffic APIs
Improve database queries

Data Retention

ℹ️ Info:

Log Retention: Logs are retained for 30 days

Analytics Data: Traffic and performance metrics are retained for 90 days

Export Data

Download your analytics and logs:

Logs: Use the Download button in the Logs tab
Analytics: Export to CSV (coming soon)
Reports: Generate PDF reports (coming soon)

API Access (Coming Soon)

Programmatic access to your deployment metrics:

// Get traffic data
GET /api/analytics/traffic?project_id=xxx&range=7d

// Get server logs
GET /api/logs/server?project_id=xxx&limit=100

// Get performance metrics
GET /api/analytics/performance?project_id=xxx

Need Help?

Review Troubleshooting for common issues
Check Best Practices for optimization tips
See Configuration for setup guidance

On this page