**Assure → Health** shows your servers and the software installed on them, with one ranked list of what needs attention. Structurell reads each server regularly and flags problems such as a disk filling up, a pending reboot, security updates waiting to be installed, or installed software with a known security advisory.

## Before you start

- Server health must be included in your package. See [Package and add-ons](/account-and-access/package-and-add-ons).
- You need permission to view server health. See [Users, teams, groups and permissions](/account-and-access/users-teams-groups-and-permissions).
- Structurell needs a connection it can use to read each server. A subscription administrator adds it under **Account → Connections**, for example an **SSH** connection to a server you run, or an **Adobe Commerce Cloud** connection to your environment. See [Connecting a provider](/connections/connecting-a-provider).

## Adding a server

1. Go to **Account → Connections** and select **New connection**.
2. Choose **SSH** as the **Provider** and give the connection a **Name**, such as the server's name.
3. Under **Credentials**, enter the **Host**, **Username** and either a **Password** or a **Private key** (with its **Private key passphrase** if it has one). Enter the server's **Host key fingerprint (SHA256)** so Structurell can confirm it is talking to the right server. **Port** and **Timeout (seconds)** are optional.
4. Select **Save**. If you see **Test connection**, select it to check Structurell can sign in.

Use a dedicated user for this connection. Structurell won't read a server as the `root` user.

The server appears on **Assure → Health** after its first reading, which can take a while. Until then its details may say "No inventory collected yet."

## The Health page

At the top, a status shows your overall health: **Healthy**, **Warning**, **Degraded** or **Critical**, taken from the most serious open item. Select the refresh button to reload the page. The time of the latest figures is shown as "Refreshed" followed by the time.

The summary tiles show:

- **Overall**: how many items need attention, broken down by severity.
- **Servers reporting**: how many of your servers have reported recently.
- **Workers running**: background worker processes that are running, stopped, or running outside management.
- **High+ advisories**: high and critical security advisories affecting your installed software.
- **Pending updates**: operating system updates waiting to be installed, with security updates counted separately.

## Needs attention

**Needs attention** lists every open problem, most severe first. Each item has a severity of **Critical**, **High**, **Warning** or **Info**. Info items are for your awareness and don't change the overall status.

Items include:

- disk space or inodes running out on a server
- a reboot required, or security updates waiting to be installed
- background programs running outside the server's normal management
- a server that couldn't be read, or hasn't been read recently
- installed software with a security advisory, software that has reached end of life, or software that is behind its latest release

Select **View** on an item to open the server or source it relates to. Items close automatically once the next reading no longer finds the problem.

## Servers and software

Below the list, two tabs show the detail.

- **Servers** lists each server with its status. Select **View** to open a server.
- **Software** shows **Installed software**: every package found on your servers and its version.

A server's page shows its status and:

- **Key versions**, such as the **Operating system**, **Kernel**, **PHP**, **Nginx**, **Redis**, **PostgreSQL** and **MariaDB**, where installed.
- Capacity and updates, such as **Disk used (fullest mount)**, **Memory used**, **Load (1 min)**, **Reboot required**, **Security updates pending**, **Advisories** and **Last inventory**. Only the figures the server reported are shown.
- **Sites** on the server, where known, with their deployment status.
- **Needs attention** for this server only.

Select **Back to health** to return.

## Using health with audits

A server you've connected can also be added to an audit target, and a schedule can run automatically when a security advisory matches software on it. See [Audits, targets and health reports](/assure-and-diagnose/audits-and-findings) and [Assurance reviews and audit schedules](/assure-and-diagnose/assurance-reviews-and-schedules).

## Troubleshooting

- **"The health summary could not be loaded."** Select the refresh button to try again.
- **A server is missing.** Check its connection on **Account → Connections** is **Enabled** and shows **Connected**, then wait for the next reading. See [Troubleshooting connections](/connections/troubleshooting-connections).
- **"This server could not be loaded."** The server may have been removed, or its connection deleted. Select **Back to health**.
- **An item keeps coming back.** It's still being found on the server. Fix the underlying problem, such as installing the pending updates, and it closes after the next reading.