To obtain more information about the devices in your inventory, you can use the Flight Control CLI or the Flight Control web console.

Each device has a unique device name and when configured at enrollment, a human-readable alias shown in the ALIAS column.

In the web console, open a device from the inventory to review status and to access the Logs tab for journal and file-based device logs. For log viewing, streaming, and download steps, see Viewing, streaming, and downloading device logs in the web console in the Additional resources section.

Prerequisites

• You must install the Flight Control CLI. See Installing the Red Hat Edge Manager CLI in the Additional resources section.
• You must log in to the Red Hat Edge Manager service.
• You must enroll at least one device.

View device inventory and device details

When vulnerability reporting is enabled, you can review a paginated table of CVEs affecting the device in the Security overview card on the device details page. For more information, see View vulnerabilities on a device in the Additional resources section.

View devices in your device inventory. Complete the following steps:

1. View the devices in the device inventory by running the following command:

   flightctl get devices

   See the following example output:

   NAME           ALIAS         OWNER   SYSTEM  UPDATED     APPLICATIONS  LAST SEEN
   <device_name>  edge-host-01  <none>  Online  Up-to-date  <none>        3 seconds ago

The ALIAS column shows the device alias label. If no alias was assigned, the column shows <none>. For more information about how aliases are set during enrollment, see Device alias and enrollment labels in the Additional resources section.

1. View the details of this device in YAML format by running the following command:

   flightctl get device/<device_name> -o yaml

   See the following example output:

   apiVersion: flightctl.io/v1alpha1
   kind: Device
   metadata:
     name: <device_name>
     labels:
       alias: edge-host-01
       region: eu-west-1
       site: factory-berlin
   spec:
     os:
       image: registry.example.com/edge/rhel:9.5
     config:
       - name: my-os-configuration
         gitRef:
           path: /configuration
           repository: my-configuration-repo
           targetRevision: production
   status:
     os:
       image: registry.example.com/edge/rhel:9.5
     capabilities:
       osMode: image
     config:
       renderedVersion: "1"
     applications: []
     applicationsSummary:
       status: Unknown
     resources:
       cpu: Healthy
       disk: Healthy
       memory: Healthy
     systemInfo:
       architecture: amd64
       bootID: 037750f7-f293-4c5b-b06e-481eef4e883f
       operatingSystem: linux
     summary:
       info: ""
       status: Online
     updated:
       status: UpToDate
     dependencySync:
       configRefs:
       - configProviderName: my-os-configuration
         fingerprint: abc123def4567890
         lastUpdatedAt: "2026-05-21T10:00:00Z"
   [...]

The status.capabilities section reports device capabilities detected by the agent. The osMode field indicates whether the device runs in image mode (bootc-based OS with transactional updates) or package mode (traditional Red Hat Enterprise Linux managed through dnf or yum). Package-mode devices report an empty status.os.image field because no bootable container image is associated with the running OS. OS identity on package-mode devices is available through status.systemInfo fields such as distroName and distroVersion.

In the Flight Control web console, the device details page displays the OS mode. Package-mode devices show N/A or empty for the system image field.

The status.systemInfo section always includes core fields such as architecture and operatingSystem. Additional built-in and custom fields appear when you enable them in the agent system-info and system-info-custom configuration. For more information, see Reporting system information from the agent in the Additional resources section.

When the device references Git, HTTP, or Kubernetes secret configuration providers, status.dependencySync.configRefs shows the upstream fingerprint last applied to the device. For more information, see Sync status on devices in the Additional resources section.

Device update status and update state

The status.updated.status field indicates whether the device’s running OS and configuration match the device spec. It can have the following values:

When an update is in progress, status.conditions includes an Updating condition whose reason field indicates the current phase. After a failed update and rollback, the reason is Error; the device has returned to the previous OS version and the agent will not retry that failed version automatically. The following update states can appear:

The status.updated.info field might contain a short message about the last transition. For troubleshooting a rollback or failed update, see Troubleshooting OS update rollback in the Additional resources section.