Infrastructure Control Server · Infrastructure overview

The deployment at a glance

Proposed interface concept Not released. A design for discussion, drawn in HTML and CSS; not a screenshot of working software.

The Infrastructure Control Server’s overview: Proxmox clusters, hosts, VMs and containers, service health, open warnings and critical alerts, resource utilization, recent incidents, upcoming maintenance and a capacity forecast with its uncertainty. It is a separate console from the workspace and from tenant administration. The figures shown are example data.

View full size Download image (WebP, 1600×899) Infrastructure operations

Proposed interface concept Not released · example data · subject to change

Office UnboundInfrastructure ControlRidgeline IT · ProductionSearch hosts, VMs, containers, services/2DO

Production1 of 4 environmentsOverviewHypervisorsContainersServicesMonitoringAlerts2Updates3CapacityRecoveryAudit logSettingsController ics-01Standby ics-02 ready

ProductionOverviewInfrastructure overviewExample data

Automation: approved actions onlyMaintenance

Hypervisors 5 hosts 2 Proxmox VE clusters

Virtual machines 24 Managed · 14 not in scope

Containers 142 139 healthy

Services 29 / 31 Healthy

Warnings 4 Open

Critical 1 Acknowledged 02:31

UtilizationNow · 30-day peak

CPU38%256 cores · 30-day peak 71%
Memory67%1,370 of 2,048 GB allocated
Storage · cluster A52%ceph-a · 31 of 60 TB
Storage · cluster B71%ceph-b · 28.4 of 40 TB · alert at 85%
Network12%25 GbE uplinks · busiest port, 30-day peak 34%

Hypervisor hostsQuorum OK

Host	CPU	Memory	Note
pve-a1Cluster A	44%	78%	Rack 1
pve-a2Cluster A	39%	76%	Rack 1
pve-a3Cluster A	31%	77%	Rack 2
pve-b1Cluster B	27%	38%	Rack 2
pve-b2Cluster B	34%	36%	Disk latency

Recent incidentsAlert center

CriticalOutbound mail relay failing on mail-02INC-2047 · 02:14 · acknowledged by D. Okafor
Warningceph-b write latency above 20 msINC-2046 · 01:52 · watching
NoticeIdentity container restarted, recoveredINC-2043 · Thu · automated restart, verified

Capacity forecastEstimate

Storage cluster B: projected to reach 85% in about 7–10 weeks at current growthEstimate from 90 days of metrics
Cluster A cannot absorb the loss of one host’s memory1,180 GB in use · 1,024 GB on two hosts
CPU headroom beyond 12 monthsSurvives loss of 1 host in both clusters

Upcoming maintenance

Sun 1502:00Document engine 2.9.0 · canaryApproved · snapshot first
Tue 1722:00Host packages, cluster ARolling · VMs live-migrated first
Sat 2102:00Mail service 1.14.3 security fixNeeds approval

Service healthApplication checks

MailRelay failing
Identity / SSOHealthy
Files and syncHealthy
DocumentsHealthy
Chat, meetingsHealthy
TelephonyHealthy
DatabasesReplica in sync
DNS and proxyHealthy
Storageceph-b latency
Backups24 of 24 last night

OverviewMonitoring2AlertsCapacityMore

The deployment on one screen: hosts, VMs, containers, service health, open incidents, maintenance and a capacity estimate.

Shape this before it is built

This screen is a proposal. MSP design partners review concepts like this one against how they actually run customers, and say what is missing.

Become an MSP design partner Register interest