16.3. Asset Detail View: Health Metrics, RMM Vitals, Hardware, and Security

Click any asset on the dashboard (or choose View details from its row menu) to open the full asset record. This view brings together the device's identity, live monitoring data, hardware, security posture, and full history on one screen.

Asset pages use the same bento layout as tickets, contacts, and the client command center: a hero band across the top, then panels arranged around a single merged timeline.

Figure 1: The asset detail bento layout. Everything that happened to the device shares one filtered timeline down the middle.

The Asset Header:

At the top of the record you'll find the asset's name and Asset Tag, along with:

• An RMM status badge (for assets connected to a remote-monitoring tool), showing whether the agent is Online, Offline, or Overdue, plus the monitoring provider's name.
• Back to Assets — return to the inventory list.
• Print — print the asset record.
• Create Ticket — log a service ticket against this asset (see 16.8. Create Tickets from Assets).
• An Actions menu with Edit Asset and Delete Asset. For RMM-managed assets, a Refresh Data option re-pulls the latest monitoring information.

The Hero Band:

Beneath the header, a hero band repeats the asset's identity — name, status badges, asset tag, serial, client, and location — above four figures that summarize its condition at a glance:

• Health: Healthy, Warning, or Critical.
• Security: Secure, or at risk.
• Open tickets: How many service tickets are currently active for the asset.
• Warranty: Days until the warranty expires, or how long ago it expired.

A warranty that reads expired 204d ago next to a device that is still in production is exactly the kind of thing this band exists to surface — and exactly the kind of finding that becomes an asset refresh opportunity.

The Merged Timeline:

The centre of the record is a single timeline where everything that has happened to the device appears in one sequence: service tickets, record changes, maintenance, reboots, and patch scans.

Filter it with the chips above the list:

A merged spine answers the question that separate tabs could not: what was happening around the time this went wrong? A patch scan two days before a ticket about repeated freezing is a lead; on separate tabs it is a coincidence nobody notices.

Each entry shows how long ago it occurred and who was involved, so the record reads as a history rather than a log.

Information Panels:

Panels sit around the timeline:

• Identity: Tag, serial, status, location, purchase date, and warranty end. The serial number and asset tag can be copied to the clipboard with a single click.
• Hardware: OS, CPU, cores, RAM, and IP address.
• Software: Installed software discovered by the RMM integration. See 16.5. Track Software Inventory.
• Notes: A rich-text notes area for operational context specific to this asset.
• Live vitals: Agent status and last check-in, CPU, memory, disk, uptime, and signed-in user. If the asset is not linked to a monitoring tool, this panel shows that it has never checked in.
• Security: Antivirus product, pending and failed patches, last scan time, and agent version.
• Related Assets: Other devices this asset is linked to. See 16.7. Link Related Assets.

Editing happens in place — click a field to change it rather than opening a separate form. Heavier panels open in a focus drawer so they have room without pushing the rest of the page down.

Existing /edit deep links continue to work and open the record in edit mode.

Where the Live Data Comes From:

The RMM vitals, hardware utilization, software inventory, and security panels are populated by a connected remote-monitoring (RMM) integration. Set up an integration — for example, NinjaOne — from Settings (see 20.4. NinjaOne RMM Integration) to begin syncing live device data into AlgaPSA.