> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-a-workspace/health-score.md).

# Health score

How the workspace health score is calculated from the online state, signal quality, and battery level of the devices in a workspace, and how to improve it.

{% hint style="info" icon="heart-pulse" %}
**Your deployment at a glance.** Monitoring a large IoT fleet can be cumbersome, and checking the online status and battery level of thousands of devices by hand takes a long time. The health score captures the state of your deployment in a single number, from **1** (bad) to **5** (good).
{% endhint %}

<figure><img src="https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2Fgit-blob-7cc255cfc295a13bb7ed385333d70a50712ee9e6%2Fworkspace-health-score-example.png?alt=media" alt="An example workspace overview with a health score of 4, its written assessment, and the device status breakdown by online status, battery level, and signal quality"><figcaption><p>The health score on the workspace overview</p></figcaption></figure>

The **health score** is computed for each [workspace](/device-management/managing-a-workspace.md). It combines three partial scores, each also rated from 1 to 5:

<table><thead><tr><th width="220">Partial score</th><th>Based on</th></tr></thead><tbody><tr><td><strong>Online score</strong></td><td>The share of devices that are online.</td></tr><tr><td><strong>Signal score</strong></td><td>The <a href="/device-management/create-new-device/devices.md#signal-quality-indicator-sqi">signal quality indicator (SQI)</a> of each device's last uplink.</td></tr><tr><td><strong>Battery score</strong></td><td>The <a href="/device-management/create-new-device/devices.md#battery-level">battery level</a> of each device's last uplink.</td></tr></tbody></table>

<figure><img src="https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2Fgit-blob-476c7e302c49b0119c3b7ba57aef17cccade449d%2Fworkspace-health-score-hierarchy.png?alt=media" alt="Demonstrating all the subscores (online_status, battery_level ...etc) flowing in the main workspace health score"><figcaption><p>Workspace metrics flowing in the health score</p></figcaption></figure>

**The health score is the average of the partial scores, but never higher than the online score.** Offline devices are therefore the quickest way to lose points: good batteries and strong signals do not help if the devices are not sending data.

Each device gets a **rating**, such as good or bad, and the workspace gets a **score** calculated from the ratings of all its devices. Scores are rounded to whole numbers, and a result below 1 counts as 1.

The score is calculated from the latest state of every device in the workspace and recalculated periodically, so it follows devices going offline, coming back online, or reporting new uplink metrics.

### Troubleshoot your IoT fleet

Start with the offline devices, as they indicate data loss due to connectivity issues.

Once all connecvity issues are resolved, you can look into battery level (e.g. scheduling next battery change) or signal quality indicator (e.g. add gateways).

{% hint style="info" %}
**Genio can help you with this troubleshooting.** You can click the button `Analyse with GenIO` on the top left card of the **Workspace overview** page. For more details, see [Use Genio to troubleshoot your fleet](/genio/genio.md#use-genio-to-troubleshoot-your-fleet).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akenza.io/device-management/managing-a-workspace/health-score.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.