> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/health.md).

# Health

The **Health** tab displays the application performance and reliability issues across your environment.

The tab combines speed, error rates, benchmark indicators, and AI-powered insights to quickly understand the impact on application users and prioritize remediation. The system calculates Health metrics over the last 30 days.

## Explore application health

The top section of the **Health** tab visualizes how application technical health evolves over time. The system calculates these metrics from the `web.page_views` NQL table.

**Benchmark** indicators help you quickly identify, using red and green color conventions, whether performance health trends are stronger or weaker than the global Nexthink benchmark.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FI1RAbYFT1UMpY2TkwQJs%2F2026.8_AppEx_12_T4vGp7.png?alt=media&#x26;token=cc0c39f2-853f-430c-9fa0-17f3790e50f7" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If no **benchmark** data is available for categorization, the system defaults to the configured performance thresholds for the target application. Refer to [Setting application thresholds](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/thresholds.md).
{% endhint %}

From the **Health** tab of the target application:

* Find at the top of the tab an overall application health rating relative to the global benchmark: **Strong, Average,** and **Weak**.
* Explore and hover over the **Speed** and **Error rate** bar chart to monitor performance behavior over time. Detect abnormal spikes or recurring issues.
* Use the **Speed** and **Error rate** gauge to quickly determine current application health behavior.
* Hover over the **Speed** or **Error rate** gauge to open the **action menu** and drill down into the specific page loads behind the aggregate.

The system defines the overall status as follows, comparing page load time and error rate against the global benchmark, or against your configured thresholds when no benchmark is available:

* **Strong**: both page load time and error rate are more than 10% better than the benchmark, or both meet the strong user threshold.
* **Average**: page load time and error rate are within 10% of the benchmark, or both meet the average user threshold. If only one metric is average or weaker, the system uses the weaker result.
* **Weak**: either page load time or error rate is more than 10% worse than the benchmark, or either meets the weak user threshold.

The **Speed** gauge shows:

* **Fast**: more than 10% better than the benchmark, or 0 to average against your configured threshold.
* **Moderate**: within 10% of the benchmark, or average to frustrating against your configured threshold.
* **Slow**: more than 10% worse than the benchmark, or higher than frustrating against your configured threshold.

The **Error rate** gauge shows:

* **Low**: more than 10% better than the benchmark, or 0.0% to 0.5% when no benchmark is available.
* **Fair**: within 10% of the benchmark, or 0.5% to 2.0% when no benchmark is available.
* **High**: more than 10% worse than the benchmark, or above 2.0% when no benchmark is available.

## Compare application health across employee groups and application features

Examine the heatmap to identify where application health issues have the highest impact across your organization.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FfktUM8uxW5cQoHxYpPO2%2F2026.8_AppEx_13_W6yCb3.png?alt=media&#x26;token=dcc3b6af-ef4b-40ec-bc1e-5b150ae352c1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Heatmap totals represent averages and are not equal to the sum of individual cell values.
{% endhint %}

From the dropdown, switch between **Health**, **Speed**, or **Error rate** to focus the analysis on overall application health, page responsiveness, or reliability issues.

* Use the first **By** filter to group the results by organizational dimensions, such as **Division**, **Department**, or **Entity**, to identify affected business areas. The available options for grouping users are determined by the **user organization fields** you configured in your Nexthink environment.
* Use the second **By** filter to narrow the results further, across:
  * The application **Features**, which are determined by the application **Key pages** configured in Nexthink.
  * Or, the device location (such as **Countries**, **States**, **Sites**, or **Location Type**) to detect where the weak experience is concentrated.

{% hint style="info" %}
On heatmaps with more than 10,000 rows, the system displays an infobar indicating that not all rows are shown, so the resulting ranking may not reflect the complete dataset.
{% endhint %}

{% hint style="warning" %}
If **user organization fields** are not fully enriched, the system may use fallback sources such as **Entra ID** data (if configured), which can affect user distribution across groups.

Refer to [Configuring user organization](/user-guide/administration/system-configuration/data-management/environment/product-configuration.md) to ensure you correctly create and enrich user organization fields.
{% endhint %}

## Investigate application insights

Review and select specific **Insights** to provide AI-powered contextual analysis highlighting the likely causes and impact of application health issues, from the **Application expert** right-side panel.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FKk3QOTNwJVm7arJmcGSm%2F2026.8_AppEx_14_Z1sHk5.png?alt=media&#x26;token=c7c2e821-6611-4e8a-afba-9dd0dfd49b3b" alt=""><figcaption></figcaption></figure>

* Why the selected health pattern matters.
* **What the data shows** for deeper analysis of potential root causes, such as system limitations or service bottlenecks, behind slow-loading pages, increased error rates, and recurrent issues impacting teams or workflows.

{% hint style="info" %}
The system displays the ✦ sparkles icon to indicate AI-generated content or insights. AI is evolving rapidly and delivering great insights, but it can still make mistakes. Nexthink recommends validating your results to ensure accuracy and support informed decision-making.

Refer to the [Nexthink Insights - AI Model Card](https://docs.nexthink.com/legal/global-ai-hub/nexthink-insights-ai-model-card) documentation for more information.
{% 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.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/health.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.