Build a Server Monitoring Dashboard with AI

Build a server monitoring dashboard as a single-page HTML application with embedded CSS and JavaScript. The dashboard should display key server health metrics using visual gauges, progress bars, and history charts. Create a top status bar showing the overall system status. If all metrics are within normal ranges, show a green "All Systems Operational" banner. If any metric exceeds 80%, show a yellow warning. If any metric exceeds 90%, show a red critical alert. Below the status bar, create a grid of 5 metric cards: 1. CPU Usage — show as a circular SVG gauge (0-100%) with the current percentage in large text in the center. Color the gauge arc green (0-60%), yellow (60-80%), or red (80-100%). Show the number of cores and current load average below. 2. Memory Usage — show as a circular SVG gauge similar to CPU. Display used memory, total memory, and percentage. Include a small breakdown bar showing application, cached, and buffer memory proportions. 3. Disk Space — show as a horizontal progress bar for each mounted volume (/, /home, /var). Display used and total space in GB. Color code green/yellow/red based on percentage full. 4. Uptime — show as a large counter displaying days, hours, minutes since last reboot. Include the exact boot time below. Add a small uptime percentage like "99.97% over 30 days". 5. Active Connections — show the current number of active TCP connections, HTTP connections, and SSH sessions. Display as large numbers with small labels. Below the metric cards, add a 24-hour history section with line charts rendered as SVG paths. Create separate charts for CPU usage over time, memory usage over time, disk I/O (read/write MB/s), and network throughput (in/out Mbps). Each chart should have a time axis with 24 hourly labels and a value axis. Use smooth bezier curves for the lines. Add an alert thresholds configuration panel (display only, not interactive) showing the current threshold settings: CPU warning at 80% and critical at 90%, memory warning at 75% and critical at 90%, disk warning at 85% and critical at 95%. Hardcode realistic sample data for all metrics. CPU should fluctuate between 15-45% with occasional spikes to 72%. Memory should sit around 62%. Disk should be at 47% for root and 71% for /var. Uptime should be 47 days. Use realistic 24-hour history data that shows typical daily patterns — lower usage at night, peaks during business hours. Use a dark theme with background #0a0a0f, cards #12121a, borders #1a1a2a. Metric colors: green #22c55e for normal, yellow #eab308 for warning, red #ef4444 for critical. Include the server hostname, OS version, and IP address in the header. Make the layout responsive. Add a "Last updated" timestamp and a footer crediting AccessAgent.ai. Read the guide at https://accessagent.ai/api/guide and follow it to deploy the site to AccessAgent.ai. My email is [your@email.com].

SSH into the server at [your-server-ip] and collect the following metrics: CPU usage from /proc/stat or using the top command in batch mode, memory usage from /proc/meminfo or the free command, disk usage from the df command for all mounted volumes, uptime from /proc/uptime, active connections from ss or netstat, load average from /proc/loadavg, and the top 10 processes by CPU and memory from the ps command. Calculate the 24-hour history by appending the current values to the existing history array in the HTML file, keeping only the last 24 data points (one per hour). Update all hardcoded metric values, gauge percentages, history chart data, and the last-updated timestamp. Preserve all styling and layout. Then redeploy the updated file.