Logs, Metrics & Real-Time Observability
Learn how TurboV captures, streams, and visualizes build logs, runtime container logs, server hardware metrics, and Traefik HTTP request traffic.
1. Real-Time Build Logs
During deployment, every compiler phase, package download, and Docker build step is streamed directly from the host to your browser:
- Live Streaming: The agent captures
stdoutandstderrfrom the build context and transmits line-by-line updates over WebSocket. - Color Coding: ANSI terminal color sequences and error highlights are preserved in the dashboard console.
- Log Archival: Build logs are permanently saved alongside the deployment record, allowing you to review past builds, debug failed dependencies, or inspect compile durations at any time.
2. Streaming Runtime Container Logs
Once an application or database is running, the TurboV Agent attaches to the Docker daemon event stream to forward logs:
[ Application Container (stdout/stderr) ]
│
▼ (Docker Engine Multiplexer)
[ TurboV Agent Daemon (VPS) ]
│
▼ (WebSocket Event: runtime:logs)
[ Dashboard UI (Browser) ]
Dashboard Log Features
- Log Level Filtering: Filter lines by severity (
INFO,WARN,ERROR). - Full-Text Search: Instantly find specific error stack traces, user IDs, or request IDs using the search bar.
- Auto-Scroll & Pause: Toggle auto-scroll to follow live traffic or pause to inspect a specific stack trace.
- Time Boundaries: Query historical logs within specific time windows (e.g. Last 1 Hour, Last 24 Hours, Custom Range).
3. Server Hardware Resource Metrics
TurboV continuously collects host resource utilization to ensure you know when a server needs scaling:
| Metric | Source | Visualization in Dashboard |
|---|---|---|
| CPU Utilization | /proc/stat & host cgroups | Real-time percentage chart with historical trends |
| Memory (RAM) | /proc/meminfo | Breakdown of Total, Used, Cached, and Swap memory |
| Disk Storage | statvfs on root / & /var/lib/turbov | Used vs Total capacity with high-usage warning thresholds |
| Network I/O | Host network interfaces | Inbound (Rx) and Outbound (Tx) bandwidth throughput |
4. Traefik HTTP Request Metrics
Because all incoming HTTP/HTTPS traffic flows through the bundled Traefik v3 reverse proxy, TurboV provides deep insights into your public traffic:
- Request Throughput (QPS): Real-time queries per second per application and domain.
- Response Latency: Visual breakdown of p50, p95, and p99 response times to detect performance regressions.
- Status Code Distribution:
2xx: Successful requests3xx: Redirections (e.g. HTTP to HTTPS)4xx: Client errors (e.g. 404 Not Found, 401 Unauthorized)5xx: Application crashes or 502 Bad Gateway alerts