Skip to content

Inventory & filters

The Fleet page is a paginated list of every agent in the active tenant. At fleet scale (≥ 1000 agents), filters and search are essential.

What each row shows

Column Source Notes
Name agent_description.host.name or fallback to instance_uid Click to open detail page
Group Single-group invariant — exactly one row per agent Click to open the group page
Health ReportsHealth capability summary Healthy / Unhealthy / Unknown
Version Agent type + version e.g. otelcol-contrib 0.115.1
Last seen UTC Click to switch to local time
Effective hash Short content hash of the running config Hover to see the full SHA

Filters

  • Health — multi-select chip filter.
  • Platform / OS — chip filter, populated from agent_description.
  • Group — chip filter, picks one or more groups.
  • Version — chip filter; useful to spot agents stuck on an old binary.
  • Capability — chip filter; "show me all agents with AcceptsPackages" before a binary rollout.
  • Drift — chip filter, shows only agents whose EffectiveHash ≠ AssignedHash.
  • Tenant (multi-tenant Admin only) — switch which tenant's view you see.

The search box matches:

  • agent name,
  • instance_uid,
  • any value in agent_description (service.name, k8s.pod.name, …).

Search is case-insensitive and substring. To search by JSONB key, type key=value (e.g. service.name=checkout) — the editor expands the match into the right query.

Label-chip filter

Click any label chip on an agent's row to add it as a filter (service.name=checkout). Click again to remove. Multiple chips combine with AND. The active filter set is reflected in the URL — copy to share.

Sorting

Sort by name, last seen, or version. The default is "last seen descending" so recently-active agents bubble to the top.

Bulk actions

Multi-select via the checkbox column, then Bulk → Move to group or Bulk → Revoke certificates. See Bulk actions for the full list.

Live updates

The list is subscribed to live updates. New agents connecting, status changes, and group moves appear without a refresh — usually within a few hundred milliseconds.

Performance notes

The query is optimized for fleets up to ~ 50 000 agents. Past that, the list paginates server-side. Filters always apply server-side regardless of fleet size.

Some advanced operations (CSV export, "select all + bulk move") cap at 10 000 rows in a single operation to avoid runaway requests; bulk operations beyond that should be scripted via the REST API.