Skip to content
User Guide

Location Detail

Open a location to see its operational summary and the resources it contains. Locations are organizational units — geographic sites, logical groupings, or a mix. Every resource belongs to at most one location (resources without a location show up in the Unassigned branch of the tree). Summary, History and Facts include permitted resources in the location and its descendants. Visible tabs and actions depend on your permissions; being able to navigate a parent location does not grant permission to edit it or change its Notes.

The page has these tabs:

  • Summary — aggregate metrics, map preview, donut charts, and permitted Compliance, Alerts, and Syslog cards.
  • Notes — free-form Markdown notes for the location, with the same editor and versioning as resource Notes.
  • Facts — appears when facts are enabled and you can read them; browses collected facts across the scope.
  • Files — browse and manage catalog files attached to the location tree. Child locations appear before files and folders, and both location and folder breadcrumbs are clickable.
  • History — the interleaved event feed (config changes, sessions, health transitions, AI agent runs, …) for the scope; same anatomy as the resource History tab.

Summary tab

Aggregates the location’s operational state at a glance:

  • Metric tiles — four counts: Resources, Healthy, Degraded, and Critical.
  • Map card — if the location has coordinates, a map pin is rendered; otherwise, a placeholder invites you to set coordinates by editing the location.
  • Connectivity Summary donut — distribution of resource statuses (Verified, Unreachable, Authentication failed, Invalid signature, etc.).
  • Health Summary donut — distribution across Healthy / Degraded / Critical / Unknown.
  • Snapshot Coverage donut — how many resources have a recent snapshot versus how many are missing one.

For individual reachability, signature, authentication, and identity outcomes, use the browse tree’s verification filter or open a resource’s Summary verification row. An invalid server signature and a mismatch with a stored resource identity are different checks.

Compliance appears below the charts as a full-width card; Alerts and Syslog share the next row and stack on smaller screens. Cards require both the relevant permission within the location subtree and the licensed capability: fact policies for Compliance, IDS for Alerts, and Collector for Syslog. Each card includes only permitted evidence from the location and its descendants.

Browsing resources

Expand the location in the Manage → Browse tree to find its resources and child locations. Use the tree’s search and filters, then click a resource to open its detail. Summary provides the location’s aggregate resource counts, health, and snapshot coverage.

Editing the location

Location metadata (name, description, parent, coordinates) is edited from the tree on the Manage → Browse page:

  1. Find the location in the tree.
  2. Click its ⋮ menu and pick Edit.
  3. Adjust fields in the modal and save.

You can also reassign the location’s parent through Move, or remove it entirely through Delete (which fails if the location still has child locations or contains resources — move or delete those first).

See Manage → Browse for the full tree workflow.

Permissions

  • Read: app.resources.read.
  • Edit / move / delete the location: app.resources.write.
  • Browse catalog content: app.files.read; create/upload/rename: app.files.write; delete: app.files.delete.