Skip to content

Agent details

Click any agent on the Fleet page to open its detail view. The page is organised by panels, each independently collapsible.

Identity

  • Display name — derived from agent_description.host.name.
  • Instance UID — agent-supplied; not a trust anchor.
  • Fingerprint — the SHA-256 of the agent's mTLS leaf cert. This is the trust anchor.
  • Agent type / version.
  • OS / platform.

Capabilities

A decoded view of the OpAMP capability bitfield the agent advertised. Each capability has a green / grey chip; hover for the protocol-level flag name.

Effective config

The exact YAML the agent reports it is running, displayed in a read-only editor with syntax highlighting.

  • Diff vs assigned — switch to a side-by-side diff against the configuration version Ampora assigned.
  • Visualize — render the same swimlane the Configuration editor shows, so you can see what the agent is actually doing.

Group

Single-group membership chip. Move opens a picker to relocate the agent — the previous group's membership is dropped atomically.

Capabilities and policies

Per-rollout policy decisions for this agent's last received push. If the policy denied, the reason chip is shown next to the rollout link.

Status history

A scrollable timeline of agent events:

  • connect / disconnect,
  • health flips,
  • effective config changes,
  • remote config status transitions,
  • package status updates (if ReportsPackageStatuses).

The timeline is the cleanest way to answer "what happened to this agent at 3:42 a.m.?".

Package statuses

If the agent advertised ReportsPackageStatuses, every installed package is shown with version, hash (truncated), state (Installing, Installed, Failed), and any agent-side error string.

Audit

Last 50 audit events that reference this agent (revocation, group move, policy denial, certificate renewal). Filter by date if you need more history.

Actions

  • Revoke certificate — opens a confirmation; on confirm, the cert is revoked, the CRL/OCSP propagate, the agent disconnects on next validation. Re-bootstrap to re-onboard.
  • Force push assigned config — re-sends the assigned config even if the hash matches. Useful after a manual restart on the agent host where the cached effective hash diverged from reality.
  • Drain — politely close the WebSocket so the agent reconnects. Useful during a load-balancer change.

Federation badge

If the agent originates from a federation peer, a Includes federation peer:<name> badge sits next to the title and the Move, Revoke, and Force push buttons are disabled — only the home server can mutate.