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.

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.

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.
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 to ensure you correctly create and enrich user organization fields.
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.

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.
Last updated
Was this helpful?