How danyalns/dc-equipment-monitor works
This repository describes a planned equipment availability-monitoring system; the tree contains no implementation source. The principal workflow is an employee viewing equipment through the frontend and REST API, while backend monitoring periodically checks registered TCP ports and stores results for status and history views. The graph represents documented target capabilities, not verified runtime behavior; relationships are based on the README.
Main entry points: backend REST API · frontend Web frontend
Components 12
Client
- Web frontend
frontend - Overview counters
frontend
Backend
- REST API
backend - Authentication and roles
backend - Equipment registry
backend - Rack management
backend - Search and filters
backend
Monitoring and data
- Periodic monitor
backend - TCP availability check
backend - Check status and history
backend - Application database
backend
Other components
- Employee
Connections 14
- Employee → Web frontend: uses
README.md - Web frontend → REST API: requests data
README.md - Web frontend → REST API: polls status
README.md - REST API → Authentication and roles: enforces roles
README.md - REST API → Equipment registry: manages records
README.md - REST API → Rack management: manages racks
README.md - REST API → Search and filters: filters records
README.md - Web frontend → Overview counters: shows counters
README.md - Periodic monitor → TCP availability check: runs periodically
README.md - Periodic monitor → Application database: reads registered devices
README.md - Periodic monitor → Application database: stores results
README.md - REST API → Application database: reads and writes
README.md - REST API → Check status and history: serves status and history
README.md - TCP availability check → Check status and history: produces check result
README.md