Infrastructure overview
What the Infrastructure area covers, its sidebar groups, how hosts are found by the agent, and how to read the overview page.
The Infrastructure area looks after the servers that run other things: hypervisors (Proxmox VE clusters and nodes and Windows Hyper-V hosts, with their virtual machines and containers), Docker hosts and their containers, NAS units, virtual desktops (Remote Desktop Services deployments, their session hosts and golden images) and web servers (Linux machines running nginx or Apache and Windows servers running IIS, the sites on them, their certificates, databases and backups). Customers you host websites for can manage their own sites in the hosting panel. Most of it is handled by the same Tenvara agent you already install on devices, so there is nothing extra to deploy, no API tokens to create on Proxmox and no control panel to install on the web server.
The same area also holds each site's network and firewalls, your customers' lines and phone systems, their domains, certificates and DNS, the cameras at their sites and your uptime checks. Those have their own sections in this knowledge base, linked from the sidebar list below.

How hosts are found
Every agent carries roles that notice what the machine is. The main ones are switched on by default:
| Role | Where it does something | What it reports |
|---|---|---|
| Hypervisor role | A Proxmox VE node (Linux, with /etc/pve and pvesh present), or a Windows server with the Hyper-V role |
The cluster, its nodes, guests, storage, backup jobs, recent tasks and backups; for Hyper-V, the host, its virtual machines, checkpoints and replication |
| Web server role | A Linux machine running nginx or Apache, or Windows Server running IIS | Services, runtimes, sites, TLS certificates, databases, disks and HTTPS checks |
| Docker host | A machine running Docker Engine or Podman | Compose projects, containers, images, volumes and networks |
| Virtual desktops | An RDS connection broker and its session hosts | The deployment, its collections, session hosts, sessions and licensing |
On any other machine the roles stay idle and quietly report that there is nothing for them to do. You can see and change which roles run in Settings > Devices and agent, and a single device can override that from its own page. NAS units are read over their own API by an agent at the site, with nothing installed on the NAS: see NAS monitoring.
Note: A host that reports in is only detected. Tenvara shows its figures straight away, but it will not run any action on it and raises no alerts for it until someone adopts it. See Proxmox clusters and nodes, Hyper-V hosts and virtual machines, Virtual desktops and Web servers.
The Infrastructure sidebar
Open Infrastructure from the rail. Under Overview (the page described below), the sidebar is in groups:
- Servers and storage:
- Hypervisors: every Proxmox cluster, standalone node and Hyper-V host, with its platform and health. Its tabs are Clusters, Detected (hosts waiting to be adopted), Proxmox VE connections, vSphere connections and Tasks (what Proxmox did and every action started from Tenvara).
- Guests: every virtual machine and container across every host. Stopped guests and Failed backups are in its Views picker.
- Docker hosts: every machine running Docker Engine or Podman. See Docker hosts and containers.
- Web servers: machines serving websites, each marked as a public website, internal only, a default page only or not serving.
- NAS and storage: NAS units read over their own API (the page heading is NAS).
- Virtual desktops: RDS deployments with the tabs Deployments, Images and Sessions.
- Web hosting:
- Websites: every website on your web servers, with the tabs All websites and WordPress (every managed WordPress site as one estate).
- Hosting accounts: the site owners and resellers who use the hosting panel, with the tabs Accounts and Plans.
- Network: Network (discovery, maps and SNMP), Firewalls and controllers, Cameras and IP addresses. See Network and domains overview and Cameras.
- Connectivity, with the Telephony and connectivity module: Lines (with the tabs All lines and Suggested lines), Phone systems and Outages and SLA. See Telephony and connectivity overview.
- Domains and certificates: Domains, DNS zones, DNS templates and Certificates, one list of every certificate with a Source filter. See Every certificate in one list and Domain and SSL monitoring.
- Monitoring: Uptime checks, the websites, VPN endpoints, mail servers and firewalls checked every few minutes. See Script, file and server checks.
- Infrastructure settings, which opens Settings > Infrastructure.
Each group follows a module: Servers and storage, Web hosting and Cameras need the Infrastructure module; Network, NAS and storage, Domains and certificates and Uptime checks need Monitoring; Connectivity needs Telephony and connectivity. A new install starts with the service desk, so switch the ones you need on in Settings > Modules.
Reading the overview
The top row sums up your hypervisor hosts:
- Nodes online: how many nodes are reporting, with the number not reporting underneath. A host that has stopped reporting shows as not reporting, and its guests and capacity are left out of the totals until it reports again.
- Guests running: running guests out of the total, split into virtual machines and containers.
- Storage: whether any storage pool is filling up (over 85% full), naming the fullest one, or Room to spare when nothing is nearly full.
- Backups: guests whose last backup failed or is overdue, and guests with no backup at all, naming the host they are on, for example "0 of 3 guests on BEA-HV01 have backups".
Below that:
- Clusters and hosts lists your clusters and standalone nodes with problems first, each with its customer, the reason for its health and current CPU and memory.
- Web servers gives server health, Sites failing their HTTPS check, Certificates expiring within 14 days and Failed backups and operations. Needs attention lists the open web server alerts, most serious first.
- Recent tasks shows what the hypervisors did and the actions started from Tenvara, newest first, with All tasks to open the Tasks tab.
- Capacity adds up CPU cores and memory on adopted and detected hosts, counting online nodes only.
- Fullest storage lists storage pools by how full they are. Shared storage counts once, not once per node.
- Backups that need a look and Open alerts list the guests and alerts that want attention.
Detected hosts get a callout of their own, with Review, until someone adopts or removes them. With a customer chosen in the customer switcher in the top bar, every page in the area shows that customer only.
Where else infrastructure shows up
- Device page: a Proxmox node's or Hyper-V host's device shows a Hypervisor block; a guest that runs the agent shows which host it runs on; a web server's device shows a Web server block; a Docker host has a Containers tab.
- Customer page: the Servers and hosting group lists that customer's hypervisors, web hosting and virtual desktops, with Network and Connectivity beside it.
- Home: one line sums up infrastructure problems.
- Search and the command menu (Ctrl K or Cmd K): jump to hypervisors, guests and tasks, find guests and nodes by name, and start or shut down a guest.
Permissions
Infrastructure has its own permission area in Roles and permissions:
| Level | What it allows |
|---|---|
| View | See every Infrastructure screen |
| Manage | Adopt and remove hypervisor hosts, run guest actions and checkpoints, refresh, run site operations on web servers, and act on containers where the role allows it |
| Administrator role | Adopt or release a web server, delete a server or site, drop a database, and switch on or use the break-glass Run a command |
If the Infrastructure module is switched off in Modules, its groups disappear for everyone. Its data is kept.
More in this section
Hypervisors
- Proxmox clusters and nodes, Managing virtual machines and containers and Proxmox tasks, backups and alerts.
- Hyper-V hosts and virtual machines: Hyper-V hosts, power actions, checkpoints and replication.
- Restarting and patching hypervisor hosts: the Hypervisor hosts group and policy, Restart needed and Restart this host.
Docker and storage
- Docker hosts and containers and Updating, backing up and managing containers.
- NAS monitoring without an agent on the NAS.
Virtual desktops
- Virtual desktops: finding and adopting deployments.
- Sessions, who is on what and connection quality.
- Golden images and Pool machines and non-persistent desktops.
- Published apps, printing and reports for virtual desktops.
Web servers and hosting
- Web servers and Public website or internal only.
- Creating and managing sites, Nextcloud, PHP apps and per-site PHP settings and WordPress sites.
- Certificates, operations and alerts.
- The hosting panel, resellers and site owners: plans, quotas and the panel your customers use.
- Windows hosting: IIS, SQL Server and MySQL: IIS sites, FTP and Windows databases.
Every job
- The live job console: the commands a long job runs and their output, as it happens.
Was this page helpful?
Thanks for the feedback.