How wfillipe/projetoping.com works
PING.COM is an academic web application for registering network devices and tracking their availability, latency, and packet loss. The user workflow runs from browser-based account and device management through the Node.js API, which validates devices, invokes ICMP checks, and records results in a local JSON file. The dashboard, problem list, history, and latency chart present those results. The README documents scheduled and immediate checks and the broader UI capabilities; some corresponding implementation details are not in the excerpts, so those links cite the README rather than implying source inspection.
Main entry points: script.js Frontend behavior · server.js Check coordination · monitoring.js Ping execution · index.html Application screens
Components 19
Browser interface
- Application screens
index.html - Frontend behavior
script.js - Network dashboard
script.js - Device details
script.js - History and chart
script.js
HTTP application
- HTTP server and API
server.js - Accounts and sessions
server.js - Device management
server.js - Check coordination
server.js - Dashboard and problems
server.js - Check history
server.js - Database persistence
server.js
ICMP monitoring
- IPv4 validation
monitoring.js - Ping execution
monitoring.js - Result classification
monitoring.js
Local data
- JSON database
db.json
Other components
- Network operator
- Web browser
- Monitored device
Connections 25
- Network operator → Web browser: uses
README.md - Web browser → Application screens: loads screens
README.md - Application screens → Frontend behavior: runs interactions
README.md - Frontend behavior → HTTP server and API: sends API requests
script.js - HTTP server and API → Application screens: serves assets
server.js - Frontend behavior → Accounts and sessions: requests account actions
script.js - Frontend behavior → Device management: manages devices
script.js - Frontend behavior → Dashboard and problems: loads dashboard
script.js - Frontend behavior → Check history: loads history
script.js - Frontend behavior → Device details: loads device data
script.js - Frontend behavior → History and chart: renders history chart
script.js - Dashboard and problems → Network dashboard: supplies summary
README.md - Dashboard and problems → Network dashboard: lists problems
README.md - Check history → History and chart: supplies checks
README.md - Device management → IPv4 validation: validates address
server.js - Device management → Check coordination: starts initial check
README.md - Check coordination → Ping execution: runs ping
server.js - Ping execution → IPv4 validation: checks address
monitoring.js - Ping execution → Monitored device: sends ICMP probes
README.md - Ping execution → Result classification: parses and classifies
monitoring.js - Check coordination → Database persistence: records check
server.js - Database persistence → JSON database: reads and writes
server.js - Accounts and sessions → Database persistence: stores account data
README.md - Check coordination → Ping execution: checks every 60 seconds
README.md - Device details → Check coordination: requests manual check
README.md