Documentation

Appearance

Networks and tags ​

Use stable fleet metadata so operators can find devices and automation can resolve the intended targets.

  • A network is an organisation-owned grouping with its own device membership and operational statistics.
  • A device class describes a product line and its deployment configuration.
  • A tag is a lowercase label used for filtering and selectors.
  • A customer and site are dedicated business and location records where those modules are enabled. They are not merely tags.

Design a taxonomy ​

Prefer a small set of documented dimensions:

text
environment:production
customer:acme
site:manchester
cohort:beta
firmware:2.2

Do not encode secrets, personal data, or frequently changing telemetry in tags. Decide who owns each namespace and how a device is cleaned up when reassigned.

Understand selectors ​

Fleet monitors and jobs can combine device class, included tags, excluded tags, and any or all matching.

  • Any includes a device matching at least one include tag.
  • All includes a device only when every include tag matches.
  • Exclude tags remove matching devices from the result.

Always review target preview. A tag edit can change the result of an existing monitor or the next job assembled from that selector.

Customer and access effects ​

Networks, groups, customer portals, and device-class access can influence what a user can see. A user who can see a tag in one view does not automatically have access to every device carrying it. Diagnose missing devices by checking effective role, group scopes, network membership, class scope, customer or portal scope, and active filters.

Operational checklist ​

  1. Define class, customer, site, environment, and rollout cohort separately.
  2. Apply metadata during provisioning where possible.
  3. Review untagged and multiply assigned devices.
  4. Preview every fleet selector before a command or policy change.
  5. Audit taxonomy changes that alter support or customer access.