How raiinzli/ihkmonitoring works
IHKMonitoring is an early-stage infrastructure monitoring dashboard with an Angular frontend and an ASP.NET API backed by PostgreSQL. The visible workflow is opening the dashboard to view device and monitor statuses; the sampled dashboard currently uses hard-coded data. The API also exposes a target-list endpoint, but the sampled frontend does not call it. The tree indicates broader device, monitor, and log domain areas; their runtime wiring is not established by the sampled source.
Main entry points: dashboard.ts Status dashboard · app.ts Root app · MonitoringDbContext.cs EF Core context · main.ts Angular bootstrap
Components 15
Dashboard frontend
- Angular bootstrap
frontend/src/main.ts - Root app
frontend/src/app/app.ts - Status dashboard
frontend/src/app/components/dashboard/dashboard/dashboard.ts - Status summary
frontend/src/app/components/dashboard/dashboard-summary/dashboard-summary.ts - Status cards
frontend/src/app/components/dashboard/dashboard-status-card/dashboard-status-card.ts - Dashboard search
frontend/src/app/components/dashboard/dashboard-searchbar/dashboard-searchbar.ts
Monitoring API
- HTTP API
backend/Monitoring.Api/Program.cs - Targets endpoint
backend/Monitoring.Api/Program.cs
Monitoring domain
- Device view model
frontend/src/app/models/device.ts - Monitor view model
frontend/src/app/models/monitors.ts - Target entity
backend/Monitoring.Api/Models/MonitoringTargets.cs - Monitor entities
backend/Monitoring.Api/Models
Persistence
- EF Core context
backend/Monitoring.Api/Data/MonitoringDbContext.cs - PostgreSQL
Other components
- Operator
Connections 12
- Operator → Angular bootstrap: opens app
- Angular bootstrap → Root app: bootstraps
- Root app → Status dashboard: renders
- Status dashboard → Status summary: renders
- Status dashboard → Status cards: renders
- Status dashboard → Device view model: uses sample data
- Device view model → Monitor view model: includes monitors
- Root app → HTTP API: tests backend
- HTTP API → Targets endpoint: maps endpoint
- Targets endpoint → EF Core context: queries targets
- EF Core context → Target entity: sets
- EF Core context → PostgreSQL: reads