Monitor & Logs
Monitor your application's health, resource usage, and view logs in real-time from the dashboard.
Application Status
The top summary card shows your application's current status at a glance.
Application Status
Status Details: Hover over the Application Status badge to see detailed information including desired/ready replicas, pod counts, and last sync time.
Disabled Status: Applications can be disabled manually or automatically when your account balance runs out. Disabled applications don't consume resources and billing is paused. You can re-enable them from the Power Control tab.
Deployment Status
Resource Usage Monitoring
Monitor CPU, Memory, and Pod usage in real-time with interactive charts powered by Prometheus.
Pod Count Chart
Track the number of running pods over time. See how auto-scaling responds to traffic changes.
What to watch for:
- • Pod count should stay within min/max bounds
- • Sudden drops may indicate pod failures
- • Gradual increases suggest traffic growth
CPU Usage Chart
Monitor CPU consumption across all pods. View as percentage of limit or absolute values (cores).
View modes:
- • Percent: CPU usage as percentage of package limit (easier to understand)
- • Absolute: Actual CPU cores used (useful for optimization)
High CPU: If CPU consistently approaches 100%, consider upgrading your package or optimizing your application.
Memory Usage Chart
Track memory consumption. Critical for identifying memory leaks and optimizing resource allocation.
Memory Issues: If memory usage approaches the limit, pods may be killed by Kubernetes (OOM - Out of Memory). Monitor closely and upgrade package if needed.
Time Range Selector
Adjust the time window for resource usage charts to analyze different time periods:
Tip: Use shorter ranges (5s-1m) for real-time monitoring. Use longer ranges (1h-1d) for trend analysis.
Auto Refresh
Enable auto-refresh to automatically update charts at regular intervals:
- 5s: Real-time monitoring (high resource usage)
- 10s-30s: Active monitoring during deployment or troubleshooting
- 1m-5m: Regular monitoring for production applications
- Off: Manual refresh only (save resources)
Build Logs
Viewing Build Logs
Build logs show the complete deployment process including Docker build output, image push, and container startup.
Log information includes:
- • Docker build steps and layer caching
- • Image push progress
- • Kubernetes resource creation
- • Container startup logs
- • Health check results
- • Error messages (if deployment fails)
Auto-refresh: Build logs auto-refresh every 2 seconds during deployment. Use pagination to navigate through long logs.
Application Logs
View real-time application logs from your running containers. Logs help you:
- Debug application errors
- Monitor application behavior
- Track request processing
- Identify performance bottlenecks
Application logs are collected from all running pods and aggregated in the Logs tab. Logs are timestamped and can be filtered by pod.
Domain Monitoring
Real-time Domain Monitoring
Monitor your application's domain availability, response time, and uptime with automatic monitoring powered by Uptime Kuma.
Monitoring features:
- • Status: Real-time up/down status (200-299 = up, anything else = down)
- • Response Time: Track response time in milliseconds
- • Uptime: 24-hour and 30-day uptime percentage
- • SSL Certificate: Automatic expiry monitoring with warnings
- • Response Time Chart: Historical data with configurable time range (1 hour to 5 years)
Auto-creation: Monitoring is automatically created when you deploy an application if your deployment package has monitoring enabled. You can also create monitoring manually from the Domain Monitoring tab.
Important: The monitoring URL must return HTTP status codes 200-299 to be considered "up". Any other status code (including 400-499) will be considered "down". Make sure your application's health check endpoint returns the correct status code.
Power Control (Disable/Enable)
Disable and Enable Applications
You can temporarily disable your applications to stop billing and resource consumption, then re-enable them when needed.
What happens when you disable:
- • All pods are scaled down to 0 (application stops running)
- • Billing stops immediately
- • Domain monitoring is paused
- • Application configuration is preserved
- • You can re-enable anytime
Re-enabling: When you enable an application, it will be redeployed with your original configuration. The deployment process will start automatically, and billing will resume once the application is running.
Auto-Disable:
If your account balance runs out, all your running applications will be automatically disabled to prevent further charges. To re-enable them:
- Top up your account balance
- Go to the Power Control tab
- Click "Enable Application"