Skip to content

Repository navigation

Infrastructure

Jump to bottom
Digitalcheffe edited this page Apr 19, 2026 · 1 revision

Infrastructure Components

Infrastructure is where NORA tracks the hardware, VMs, hosts, and services your apps run on. Components are first-class — standalone or the parents of apps, with their own status, polling, and detail pages.

List page

Two tabs along the top:

  • Components tab — card per registered component (icon, name, type, IP, status dot). Click to open detail. Gear opens the edit modal. + Add Component button top-right.
  • Containers tab — table of every container discovered across Docker engines and Portainer endpoints. Columns: container name, image, source (Docker / Portainer), status, linked app. Click a row to open Container Detail.

Above the tabs, a stats strip shows overall counts — online / degraded / offline, a breakdown by type, total containers.

Supported component types

Type Use for
Proxmox Node Proxmox VE host. NORA polls the Proxmox API for VM/LXC inventory, storage pools, resource usage.
VM (Linux / Windows / Other) An individual VM, usually a child of a Proxmox node.
Linux Host / Windows Host / Generic Host Bare-metal or cloud VM not managed by Proxmox.
Synology A Synology NAS. Polls the DSM API for volumes, disks, uptime.
Docker Engine Direct Docker-socket access, usually on a VM or host.
Portainer Multi-endpoint Docker fleet via the Portainer API.
Traefik Reverse proxy with service discovery — auto-creates URL + SSL checks for every discovered route.

Each type has its own credential form (API token, username + password, or none). The edit modal also takes an optional parent field — the node/VM/host this component lives on. Parent relationships are enforced by the topology rules documented on the Relationships page.

Adding a component

Click + Add Component, pick the type, fill in the credentials. A few integration-specific notes:

  • Proxmox — create a token for root@pam or a dedicated monitoring user (Datacenter → Permissions → API Tokens). Proxmox uses a self-signed cert by default; NORA does not verify TLS for Proxmox API calls.
  • Synology — session-based auth against DSM using an admin username and password. Credentials are stored encrypted.
  • SNMP hosts (Linux / Windows / generic) — support v2c (community string) and v3 (username + auth protocol / password + privacy protocol / password).
  • Traefik — enable the API in your Traefik config. Adding the Traefik component causes NORA to auto-create URL + SSL checks for every router.

Component detail page

The detail page adapts to the component type:

  • Proxmox Node — three sections: node overview (CPU / memory / disk meters), storage pools table, VMs & LXC table. Plus a "Recent Task Failures" section covering the last 7 days.
  • Synology — volumes, disks, DSM version, uptime.
  • Docker Engine — container inventory with live status; a discovery refresh button.
  • Portainer — endpoints list, containers per endpoint.
  • Traefik — routers and services, with counts and health.
  • SNMP-polled hosts — System Info, CPU & Memory, Disk sections.
  • Generic (everything else) — CPU / memory / disk bars from resource rollups.

Every detail page has:

  • Discover Now — manually triggers a fresh scan and resource poll for this component.
  • Edit — opens the same edit modal used when adding.
  • Back to Infrastructure breadcrumb.

Container Detail page

Opened from a row on the Containers tab.

  • Header — container name, status, last-seen time.
  • Image section — full image name, update available badge (populated by WUD / DIUN or NORA's daily image scan), image digest, last-checked timestamp.
  • Linked app — which NORA app this container is associated with. Dropdown to change or unlink.
  • Ports, Networks, Volumes — expandable tables.
  • Environment variables — filtered to hide any key containing password, token, key, secret, auth, or credential. A Show all toggle reveals raw values including secrets — use with care.
  • Labels — Docker labels as key/value.
  • Delete button (top right, v1.2.1+) — removes this container's record from NORA. Doesn't touch the container on its engine. Useful for clearing ghost records after a docker compose up rename.

Topology / Relationships

The Relationships page is where you link apps to containers, Traefik routes, and infrastructure parents. Valid parent/child combinations are enforced (e.g., VMs belong under Proxmox nodes; Docker engines belong under a host). See that page for the full topology matrix.

App Detail pages render an infrastructure chain (right column on desktop) when relationships exist — a vertical visualization of the components an app runs on.

See also

  • Relationships — linking apps, containers, checks, and parents
  • Monitor Checks — Traefik-managed auto-created checks
  • Jobs — infrastructure polling cadence and manual re-runs

Clone this wiki locally