project

Server Health Monitor

Python · Flask · Data viz · view on github

Try it live · Opening the demo is faster than reading the write-up.

Open Live Demo →

A Flask server-health dashboard covering the full path from data in to alerts out. Open the page and you get a demo analysis; you can also upload your own CSV / JSON.

Features

  • Upload: CSV / JSON with cpu / ram / disk / network fields
  • Cleaning: fill missing values, fix negatives, drop duplicates, plus a cleaning report
  • Threshold alerts: CPU / RAM / disk / network over threshold are flagged with a popup
  • Charts: line, bar, pie, and scatter

Data sources

Demo and sample data are based on the Kaggle LogHub datasets (original course-assignment log sources):

Processed into server performance metrics for this board; demo_with_issues.csv injects missing values and duplicate rows on top of real data to show cleaning.

Why it matters to me

Monitoring is ops’ eyes. Small as this project is, it made me walk “collect → clean → decide → present” by hand — so when I look at Zabbix or Prometheus later, the underlying idea still matches.

Live demo — homepage already loads demo data.

一个用 Flask 搭建的服务器健康监控看板,覆盖从数据进入到告警展示的完整链路。打开页面即展示演示分析结果,也支持上传自己的 CSV / JSON。

功能

  • 数据上传:支持 CSV / JSON,需包含 cpu / ram / disk / network 字段
  • 数据清洗:缺失值填充、负值修正、重复行去除,并附清洗报告
  • 阈值告警:CPU / RAM / 磁盘 / 网络超阈值自动标记并弹窗提示
  • 可视化:折线图、柱状图、饼图、散点图四种图表

数据来源

演示与真实样本数据基于 Kaggle LogHub 数据集(课程作业原始日志来源):

经加工为服务器性能指标后用于本看板展示;demo_with_issues.csv 在真实数据基础上注入了缺失值与重复行,用于演示清洗能力。

为什么它对我重要

监控是运维的眼睛。这个项目虽然小,但让我把「采集 → 清洗 → 判断 → 呈现」这条监控的基本逻辑亲手走通了一遍——之后再看 Zabbix、Prometheus 这些工业级方案时,底层思路是相通的。

在线演示 可直接体验,首页已预载演示数据。