How josearielnunezjan/monitoreo_de_sistemas works
Project type and purpose
• This is a lightweight, real-time system-monitoring solution with three main user‐facing components:
a. A web client (HTML/CSS/JS)
b. An Android client (Monitoreo de Sistemas_1_1.0.apk)
c. A Node.js backend that gathers OS metrics and broadcasts updates via WebSockets
• Its goal is to display CPU, memory, disk, and network stats in real time for educational/lab environments.
File structure
• Top level
• Aplicación/Monitoreo de Sistemas_1_1.0.apk → Android installer package
• backend/server.js → Node.js + Express + Socket.IO server entry point
• frontend/index.html, index.js, index.css → responsive UI with Bootstrap, FontAwesome, Socket.IO client
• README.md → project description, tech stack, usage notes
• No database directory or ORM files → data flows directly from OS to clients via in-memory Pub/Sub
• The “Systeminformation” library in server.js reads hardware stats; Socket.IO pushes them to all connected clients
README for additional insights
• Confirms the tech stack (Node.js/Express/Socket.IO, Bootstrap 5, FontAwesome)
• Describes real-time monitoring features (CPU model/temp, RAM usage, disk partitions/SWAP, network per interface)
• No mention of persistence layer or external APIs beyond Systeminformation
Final advice
• Every active component and its protocol
• Don’t omit the Systeminformation module nor the APK client