Real-time system observability
Monitoring is the system health dashboard in General Bots Suite. Track CPU, RAM, disk, and network usage in real time. Monitor service status across BotServer, PostgreSQL, Valkey, MinIO, and all other components. Investigate logs, configure alerts, and ensure your infrastructure remains healthy.
Metric Description
CPU Usage Real-time processor utilization RAM Usage Memory consumption and availability Disk Usage Storage capacity and I/O Network Bandwidth and connection stats Uptime System availability percentage
Service Status Indicators
BotServer Running, stopped, degraded PostgreSQL Connection pool, query latency Valkey Memory, hit rate, connections MinIO Storage, request throughput Qdrant Vector operations, indexing Zitadel Authentication, session count
Chart Timeframe
CPU History Last 1h, 6h, 24h, 7d Memory Trends Allocation, garbage collection Request Rate Requests per second Error Rate 4xx and 5xx responses Latency P50, P95, P99 response times
Filter Description
Component Filter by service name Level ERROR, WARN, INFO, DEBUG Time Range Last 5m, 15m, 1h, 24h Search Full-text search across logs Export Download filtered logs as JSON
Alert Threshold Severity
High CPU > 80% for 5 min Warning Critical CPU > 95% for 2 min Critical Low Disk < 20% free Warning Memory Pressure > 90% used Warning Service Down Status != running Critical
Shortcut Action
RRefresh all metrics G then DGo to Dashboard G then SGo to Services G then LGo to Logs G then AGo to Alerts FToggle fullscreen chart EscapeClose modal
📊 System Health Report
CPU: 42% | RAM: 68% | Disk: 55%
✅ BotServer: Running
✅ PostgreSQL: Running (3ms avg)
✅ Valkey: Running (98% hit rate)
✅ MinIO: Running (12GB used)
Uptime: 14 days, 6 hours
09:00
📋 Recent Logs (last 5 minutes)
🔴 ERROR [BotServer] Connection pool exhausted at 10:28
🟡 WARN [PostgreSQL] Slow query detected (2.3s) at 10:27
🟢 INFO [DriveMonitor] Bot sync complete at 10:26
🟢 INFO [BotServer] Session cleanup at 10:25
[View Full Logs] [Export]
10:30
How is PostgreSQL performing?
11:00
🐘 PostgreSQL Status
Status: Running | Uptime: 14d 6h
Connections: 12/100 | Pool: Active
Avg Query Time: 3ms | Slow Queries: 2
Database Size: 2.4 GB | Tables: 18
Last Backup: Today at 03:00 AM
11:00
Endpoint Method Description
/api/monitoring/healthGET Overall system health /api/monitoring/metricsGET Current system metrics /api/monitoring/metrics/:serviceGET Service-specific metrics /api/monitoring/logsGET Search and filter logs /api/monitoring/servicesGET List all services and status /api/monitoring/services/:nameGET Detailed service status /api/monitoring/alertsGET Active alerts /api/monitoring/alertsPOST Create alert rule /api/monitoring/alerts/:idDELETE Remove alert rule
{
"status": "healthy",
"uptime_seconds": 1209600,
"cpu_percent": 42.5,
"memory_percent": 68.2,
"disk_percent": 55.1,
"services": {
"botserver": { "status": "running", "pid": 1234 },
"postgresql": { "status": "running", "connections": 12 },
"valkey": { "status": "running", "memory_used_mb": 256 },
"minio": { "status": "running", "storage_gb": 12.4 }
}
}
{
"component": "botserver",
"level": "ERROR",
"since": "2025-05-15T10:00:00Z",
"limit": 50,
"search": "connection"
}
Monitoring thresholds can be configured in config.csv:
key,value
metrics-retention,30d
log-retention,7d
alert-cpu-warning,80
alert-cpu-critical,95
alert-disk-warning,20
alert-memory-warning,90
Check Valkey connectivity (metrics are cached)
Verify the monitoring service is running
Check for clock drift between services
Refresh the dashboard manually with R
Verify log retention policy hasn’t expired entries
Check disk space for log storage
Ensure log level is set appropriately
Check component is writing to expected log path
Verify alert thresholds are configured
Check notification channels are active
Ensure the alert service is running
Review alert history for suppressed notifications
