Skip to content

Host detail page

After creating a host (or clicking one from the hosts overview) you land on the host detail page. It's organized into tabs; which tabs show up depends on the host.

Tabs

Tab When visible
Overview always (default)
Telemetry agent hosts only
Docker Linux agent hosts on which Docker was detected — after clicking "Docker detected"
Device only when a check feeds a device visualisation (switch port map, UPS panel, NAS disk bay, firewall)
Logs agent hosts only
History always — views Check history, Changes and (with anomaly detection) Analysis

Following a link to a tab that isn't available for this host silently lands you on Overview — no error message.

Overview

Header card + health strip + StatusPillsBar + optionally a telemetry or device snapshot, then the checks table below (the heart of the page). If a monitoring source is offline, a hint appears: "{{source}} offline since … — {{count}} checks aren't receiving data."

Telemetry

A dense metric grid: every figure as a cell with live sparkline and peak marker, CPU and RAM curves filled from the check history the moment you open it. If the agent delivers hardware data, cells for the real CPU load (plus iowait/steal), disks (SMART health, temperature, wear, read/write rates per drive), temperatures (all sensors with a warning traffic light) and the live throughput of the network interfaces are added — only on hosts that really deliver this data. Every cell explains itself behind the ? symbol. Below: the deep-analysis sections (hardware/inventory/network/security/lifecycle).

Docker

Every container with status, health, CPU, RAM, network, restarts, ports and uptime; project filters at the top. The basis is the Containers (Docker) check with required and exception lists (wildcards allowed) — it reports unhealthy containers, crash loops and exited auto-restart containers and carries thresholds on the number of problems. The "Per container" graph shows the CPU history per container.

Device

A device visualisation — switch port map, UPS panel, NAS disk bay or firewall. It is fed by any check that delivers a device snapshot (SNMP or agent script) and always shows the latest run.

Logs

Collected agent logs.

History

  • Check history — every stored value and status change of this device: the same console as the Global Log, restricted to the host. Your own tabs and filters apply to every device. Whoever may see the device may also see its past — the Viewer role needs no diagnostic log permission for it.
  • Changes — the change history of the host and its checks (thresholds, intervals, created/deleted).
  • Analysis — anomaly section, if anomaly detection is active.

A back link says "Back to hosts". The card shows:

  • Profile icon, colored by the worst current status
  • Heading = display name (or hostname, if none set)
  • Line 2: hostname, IP as a mono chip, profile/type, tag chips
  • Dependency chip — "depends on: {{name}}" or "{{count}} dependencies", with actions "Manage dependencies …" and "Show on map"
  • Maintenance chip (violet) — "Maintenance until {{until}}" or "Downtime"
  • Description, a note strip
  • Source chips — which monitoring sources are active (agent/collector/active checker), with an uptime popover per source

Top right: "Show on map" and "Manage host" (opens the manage panel — general tab for name, description, tags, site). When space is tight both shrink to their icons instead of dropping into a row of their own.

Compact mode

The toggle on the right of the header collapses it into one line: name, health, status pills (still usable as filters), telemetry and all actions as small icons — so the checks move up. Description, tags and explanatory texts stay in the expanded header, one click away.

The choice is stored per user on the server and applies to all devices and all browsers. Depending on the available width the collapsed header picks one of three arrangements (single line · title on top with state below · stacked); on a phone the icon buttons sit in their own row below the name.

There's no separate site chip in the header — the site is set via "Manage host" (see Sites).

Health score

The Health badge shows a colored dot, the word "Health" and the score as "{score} /100" (green from 90, amber from 70, otherwise red).

Formula:

Score = (OK checks + WARNING checks × 0.5) / max(1, open checks) × 100

Only open (non-suppressed) active checks are counted — downtime and accepted checks leave the denominator, "In progress" still counts as an open problem. As long as a host has any problem, the score is capped at 99 — a single WARNING never rounds up to 100.

Tooltip: "Score over open checks: OK counts fully, WARNING half. Downtime & accepted are excluded; „in progress" still counts as an open problem."

Subtext: "{{ok}}/{{active}} checks OK", plus for problems "{{count}} need attention", and whenever checks were excluded, always "excluding downtime & accepted ({{count}})".

StatusPillsBar

Two groups, separated by a divider:

  • Status group (every active check counts exactly once): Critical, Warning, No Data, Pending, Unknown, OK, Info (teal — checks in info mode, whatever their real status)
  • Treatment group: ACK (marked as error) ("in progress"), ACK (marked as no error) (Accepted), Downtime (violet)

Freshly created checks ("awaiting data") do not lower the health score — they form their own blue pending share; info-mode checks never count as a problem. During flapping the status tooltip of a row says whether a notification really goes out (with channels) or why not — downtime, ACK, info mode, no matching rule, status filter or no active channel.

Each pill is a filter toggle for the checks table below. Pills with a count of 0 aren't shown.

Checks table

Columns (resizable except checkbox/status/check/action):

Column Note
Checkbox for bulk actions
Status color dot
Check name + "type · mode badge" (active checker/collector/agent)
Message flexible absorber — takes up remaining width
Value incl. sparkline
Last change relative (e.g. "3 min ago")
Last checked absolute, hidden by default
Action per row

Checks with a reachability hint show a radar icon; checks in info mode show a teal "Info" badge (info-mode checks never alert, but keep running visibly — see the alerting concepts).

PENDING

A freshly created check without a first result shows status PENDING — rendered as a blue indicator with the short label "WAITING". Conceptually: "waiting for data", not an error state.

The status holds until the agent or collector has actually measured (from v1.9.442). Before that, the server tried to run a freshly created agent or collector check itself and stored that non-result as UNKNOWN — the blue status was gone within seconds. The check is still handed to its execution point immediately; the first result arrives with its next fetch, not only after the interval.

Inactive checks

Disabled checks are hidden by default. A pill "{{count}} disabled" shows them.

Bulk actions on checks

Via the checkbox column, several checks can be handled at once:

  • ACK (n)
  • Downtime (n)
  • Edit (n)
  • "Check now" — only for checks with check_mode='active'
  • Disable / Enable
  • Delete — moves to trash ("…will be moved to the trash and can be restored from there.")

Select-all only picks what you see

If the table is filtered, "select all" only picks the visible rows — a bulk action never touches a check hidden by the filter.

Check detail panel

Clicking a row opens the detail panel on the right (URL parameter, so it's shareable/linkable). Close with Esc or X, navigate with ↑/↓. The underlying data list is unfiltered — the panel stays open even if the check recovers to OK in the meantime.

"Edit" in the panel opens the configuration tab. The panel and "Manage host" are mutually exclusive — both dock on the same right side.

Besides message and graph the panel shows the rich result details a check delivers (tables, lists, figures — e.g. top processes for the load check, the VM list for Hyper-V, backup jobs), for info checks the real status on click, the threshold reasoning ("71 % ≥ 50 % ⇒ WARNING · warning from 50 % — from the profile") right next to the measured value, the delivery journal ("Recent deliveries") and, for multi-value checks, a graph with a clickable legend (drives, load 1/5/15, series from scripts).

Full screen: clicking "Full screen" opens the check in the same tab (Ctrl/Cmd or middle click in a new one) — three tabs Analysis (graph with time range 1 h to 1 year plus custom range), Status (full message and details) and Configuration (all settings in full width, next to what the check type probes and how its status is derived). Status, value and message stay above the tabs; the tab is part of the URL and can be shared.

Device scan (formerly a separate SNMP sensor picker button)

For every host with a network target (except pure agent hosts), the checks toolbar has a secondary button "Device scan" (tooltip: "Tries known vendor checks against the device and suggests available ones (optionally: deep SNMP walk)").

The button opens a modal with a collapsible section "Search deeper (walk)" — that mounts the actual SNMP sensor picker (see SNMP sensor picker) directly inside the modal. If an SNMP community is missing, the modal asks for one first.

The former separate "Pick SNMP sensors" button no longer exists — the walk is now part of the device scan.

Tags

  • Manual tags: solid chip border.
  • Policy tags: dashed chip border, tooltip "Assigned by policy — maintained on policy sync", not clickable.

What's shown/filtered is always the union of manual and policy tags.

Edit via "Manage host" → General tab, label "Tags (e.g. production, backup — matched in policies)". An input field (placeholder "Type a tag + Enter…") accepts new tags; below it, suggestion chips ("Suggestions:") from the tenant-wide tag vocabulary appear (up to 12, click to apply) — this prevents typo variants of the same tag.

On the hosts overview, a multiselect dropdown "{tag} ({count})" filters case-insensitively against manual + policy tags; the option only appears if tags exist in the tenant.

Sites

A host can be assigned a site — both when creating it ("More details" in the form) and later (Manage host → General tab, below name/description).

The field is labeled "Site" in the UI: a searchable, clearable dropdown over all sites of the tenant (empty option "No site") plus a "+" to create a new site inline (name + optional place search for lat/lon).

Separately there's a free geo override: "Custom location override (optional)" — for when a device is geographically different from its assigned site.

On the backend, the site is the sole source of geo truth: when a coordinate is needed (e.g. for physical maps), a host's own coordinate wins over the site's coordinate, otherwise the site's coordinate is used.

Delete & trash

Deleting a host in the UI is always a soft delete: the host (cascading to its checks) moves to the trash. All confirmation dialogs phrase it that way too ("…to the trash") rather than "delete permanently".

Restore via the Trash page (scope-dependent: own/tenant/system trash). It has tabs per object type — including "Host" — plus "All", services, dashboards, maps, alert rules, notifications, collectors, scripts. "Restore" per row brings the object back.

A background job permanently purges trash entries older than 30 days.

Next