InfraView

A unified self-hosted infrastructure dashboard that combines data from Netdata, Uptime Kuma, UniFi, and Backrest into one clean interface.

Features

• System Metrics (Netdata): CPU, RAM, disk, network KPI cards with live area charts (10-minute window, 5s refresh)
• Uptime Monitors (Uptime Kuma): Monitor status cards with response times, certificate expiry, and up/down counts
• Network (UniFi): WAN status with throughput, client counts (WiFi/wired), AP and switch overview, per-device cards with uptime and firmware
• Backup Status (Backrest): Repository overview and backup plan cards with last run status and timing
• Settings UI: Configure service endpoints through the web interface — no config files needed
• Dark / Light Mode: Toggle between themes
• Auto-refresh: Data refreshes automatically at appropriate intervals per service
• Environment seeding: Pre-configure services via environment variables on first launch

Quick Start with Docker

cp .env.example .env
# Edit .env with your service URLs and credentials
docker compose up -d

Open http://localhost:3080 and your services should appear on the dashboard.

The repo ships with a pre-built dist/ directory (including node_modules), so no compilation or network access is needed during docker build — it just copies files. Builds are fast even on low-powered hardware like NAS devices.

Quick Start without Docker

The pre-built output is included in the repo, so you can run directly:

NODE_ENV=production node dist/index.cjs

Open http://localhost:5000.

Configuration

Option 1: Environment Variables (recommended for Docker)

Copy .env.example to .env and fill in your values. These are used to seed the database on first launch only — after that, manage everything from the Settings page.

NETDATA_URL=http://your-host:19999
UPTIMEKUMA_URL=http://your-host:3001
UPTIMEKUMA_API_KEY=your_prometheus_api_key
BACKREST_URL=http://your-host:9898
BACKREST_USERNAME=your_username
BACKREST_PASSWORD=your_password
UNIFI_URL=https://your-gateway-ip
UNIFI_API_KEY=your_unifi_api_key

Option 2: Web UI

Navigate to Settings (gear icon) and add services manually.

Service Setup Notes

Netdata

• Uses the Agent REST API (/api/v1/data, /api/v1/info, /api/v1/alarms)
• No authentication required by default

Uptime Kuma

• Reads from the /metrics Prometheus endpoint
• Supports basic auth (username/password) or a Prometheus API key

UniFi

• Uses the local Network API (/proxy/network/api/s/default/stat/...)
• Authenticates via X-API-KEY header — generate one under UniFi Network > Settings > Control Plane > Integrations
• Self-signed certificates are accepted automatically

Backrest

• Connects via the gRPC-Web/Connect protocol (/v1/GetConfig, /v1/GetOperations)
• Uses basic auth with your Backrest credentials

Docker Networking

If your monitored services run on the Docker host (common for NAS setups):

# In docker-compose.yml, uncomment:
extra_hosts:
  - "host.docker.internal:host-gateway"

Then use http://host.docker.internal:<port> as the service URL.

If services are on the same Docker network, use container names directly.

Architecture

• Frontend: React + Tailwind CSS + shadcn/ui + Recharts
• Backend: Express.js proxy (avoids CORS issues with your services)
• Database: SQLite for service configuration storage
• Data flow: Browser → Express proxy → Your services' APIs

The repo includes the fully pre-built dist/ directory with all runtime dependencies, so Docker builds require zero network access or compilation. The Dockerfile simply copies the files in.

Development

To make changes to the source and rebuild:

npm install
npm run dev

Dev server runs on port 5000 with hot reload.

To rebuild the production bundle after making changes:

npm run build
cd dist && npm install && cd ..

This regenerates the dist/ directory. Commit the updated dist/ (including dist/node_modules) if you want your Docker builds to pick up the changes.

License

MIT