Device view¶
The Device tab of the host detail page shows a view built from blocks on the same canvas as a dashboard: arrange, resize, add, remove and label blocks. The difference to a dashboard: the device is fixed — every block shows data of this device.
Three levels¶
| Level | What | Who changes it |
|---|---|---|
| Template | Built in per device kind: switch (ports), NAS (disks & volumes), UPS, firewall, internet line | Vesana (updates) |
| Profile | Changes for every device with this profile, in every tenant | Super admins |
| Device | Changes for this one device only | whoever may edit the device |
Every level stores only what it does differently. When the template or the profile changes later, every device gets it — except exactly what a device changed itself. A device without a template (e.g. a server) gets the tab as soon as it has a view of its own.
Editing¶
"Edit view" above the view (or Manage host → General → Edit view). The panel with the blocks opens on the right; clicking a block in the view shows its settings.
- Save for — "This device" or "Whole profile" (super admins only, with the number of devices). Saving for the profile takes over the view as it is shown right now; own changes of this device that then equal the profile disappear.
- Note — shown in the history.
- Undo / Redo — also Ctrl+Z / Ctrl+Y; Ctrl+Enter saves, Del removes the selected block.
- Reset — discards the device's own changes (it shows the profile view again) or the profile's (super admin).
- History (clock icon) — every save with time and note; Restore brings an old state back as a new state.
On a phone the view is view-only. Super admins also open the profile view from the Profiles page (row menu → Edit device view); it is then edited on a device of the profile.
Blocks¶
| Block | Shows | Settings |
|---|---|---|
| Ports | Ports of a switch/router with status, speed, PoE, neighbours | Parts (header, ports, details), label per port, uplink marker, hide ports |
| Disks & volumes | Bays, system, volumes, RAID, SMART | Parts one by one, label per bay |
| UPS | State, battery, load, power | Parts one by one |
| Firewall | Header, key figures, interfaces, VPN tunnels | Parts one by one, hide interfaces |
| Internet line | Speed test results | — |
| Value from the device | One value from the device data, e.g. disks.*.temperature with "Highest" |
Aggregate, display, unit, decimals, own warning/critical limits |
| Table from the device | A list from the device data, e.g. volumes |
Columns, sorting, row count |
| Number, gauge, graph | Checks of this device | as on a dashboard; the check is chosen by name |
| Text | Note | as on a dashboard |
Parts of a panel can be hidden one by one — two "Disks & volumes" blocks, one with the bays only and one with the volumes only, make an arrangement of your own.
Ports and interfaces are addressed by their name (e.g. ether3 or GigabitEthernet0/3), never by an internal number — that changes on some devices. Checks are chosen by name, so a profile view finds the check of the same name on every device of the profile.
Device data¶
"Value" and "Table" read the data the device snapshot delivers (SNMP table or agent script). A path consists of parts separated by dots; * stands for every entry of a list:
| Path | Meaning |
|---|---|
cpu_percent |
one single value |
disks.*.temperature |
the temperature of every disk — with "Highest" the hottest |
interfaces.*.in_errors |
the input errors of every interface — with "Sum" all together |
disks.0.model |
the model of the first disk |
The picker in the panel only offers paths the device delivers right now, with an example value.
Changing it via AI¶
With an AI access Claude can change the view — for example "label port 3 on the switch as printer and mark port 24 as uplink" or "show the highest disk temperature big on all Synologys, for the whole profile". The AI reads which data the device delivers, validates the view before saving and gets the exact location and the possible values back on an error. It has exactly your rights: the whole profile only if you are a super admin. Every change is in the history of the view and in the device's History → Changes tab.
The endpoints (for your own automation): GET/PUT/DELETE /api/v1/hosts/{id}/device-view, …/device-view/fields, …/device-view/check, …/device-view/versions; the same under /api/v1/profiles/{id}/device-view; blocks and options under GET /api/v1/device-views/blocks.
Vesana library¶
The profile view travels with the profile bundle. An update from the Vesana library replaces the profile view only as long as it was not edited on the instance itself; own changes on devices always stay.