Monitoring & Logs

Deployment Logs

Every deployment generates build logs that show the full build process. Access them from:

• Dashboard → Sites → [Site] → Deployments → Click any deployment
• AI Assistant → "Show me the deploy logs for my-site"

What deployment logs include

• Git clone output
• Dependency installation (npm install, etc.)
• Build command output
• Container image creation
• Health check verification
• Final deployment status

Example deployment log

[2026-05-20 14:30:01] Cloning repository...
[2026-05-20 14:30:03] ✓ Cloned main branch (commit abc1234)
[2026-05-20 14:30:04] Installing dependencies...
[2026-05-20 14:30:18] ✓ npm install completed (847 packages)
[2026-05-20 14:30:19] Running build command: npm run build
[2026-05-20 14:30:45] ✓ Build completed successfully
[2026-05-20 14:30:46] Creating container image...
[2026-05-20 14:30:52] ✓ Image built (234MB)
[2026-05-20 14:30:53] Starting container...
[2026-05-20 14:30:55] ✓ Health check passed
[2026-05-20 14:30:55] ✓ Deployment successful!

Runtime Logs

Runtime logs capture your application's stdout and stderr output while running. These include:

• Application startup messages
• Request logs (if your app logs them)
• Error messages and stack traces
• Custom console.log output
• Unhandled exceptions

Viewing runtime logs

From the dashboard, navigate to Sites → [Site] → Logs tab. Logs stream in real-time.

Via the AI assistant:

"Show me the runtime logs for my-site"
"Show me the last 50 lines of logs for my-app"
"Are there any errors in my-site's logs?"

Log levels

We capture all output from your application. For structured logging, we recommend using levels:

Resource Usage

Monitor your container's resource consumption from the site detail page:

Metrics tracked

Resource alerts

You'll receive notifications when:

• Memory usage exceeds 80% of your plan limit
• Disk usage exceeds 90%
• Container restarts due to OOM (Out of Memory)

Deployment History

Every deployment is tracked with:

• Timestamp — When the deployment was triggered
• Duration — Total build + deploy time
• Status — Success, failed, or cancelled
• Trigger — Manual, git push, or API
• Commit hash — The exact Git commit deployed

You can rollback to any previous successful deployment from the deployment history.

Health Checks

Hostwares automatically monitors your containers with health checks:

• HTTP check — Pings your app's port every 30 seconds
• Process check — Ensures the main process is running
• Auto-restart — Containers that fail 3 consecutive health checks are restarted automatically

If your app needs a specific health endpoint, configure it in site settings:

Health check path: /api/health
Expected status: 200
Interval: 30s
Timeout: 5s

AI Log Analysis

The AI assistant excels at log analysis. Ask it to:

"Why did my last deployment fail?"
"Are there any recurring errors in my logs?"
"What caused the 502 errors yesterday?"
"Analyze my app's startup time from logs"

The AI reads your actual logs, identifies patterns, and provides actionable recommendations. This costs 3 credits per analysis.

Log Retention

Need longer retention? Contact support for enterprise log archival options.