> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics.md).

# Working with Diagnostics

{% hint style="info" %}
Nexthink Administrators should enable permissions to ensure access to Diagnostics features. 

Refer to the [Roles > Alerts and Diagnostics](/platform/user-guide/administration/account-management/roles.md#roles-alerts) and [View domain > Diagnostics](/platform/user-guide/administration/account-management/roles/view-domain.md#diagnostics) documentation for a detailed description of **Permissions** and **View domain** options.
{% endhint %}

Diagnostics are an effective set of tools and dashboards for assessing and troubleshooting various IT issues. Diagnostics are integrated throughout the product.

* The Diagnostics panel is integrated directly into the Applications module to aid in troubleshooting application issues, such as execution crashes for desktop apps. Refer to the [Monitoring desktop applications](/platform/user-guide/applications/monitoring-applications/monitoring-desktop-applications.md#employees-with-crashes) documentation for more information.
* The [Diagnostics for alerted issues](/platform/user-guide/alerts-and-diagnostics/getting-started-with-alerts/responding-to-alerts/diagnostics-for-alerted-issues.md) dashboard is directly connected to the drill-down options on the Alerts overview page.
* Drill down on issues using diagnostics from Device View.

## Accessing Diagnostics <a href="#gettingstartedwithdiagnostics-accessingdiagnostics" id="gettingstartedwithdiagnostics-accessingdiagnostics"></a>

* Select **Alerts and Diagnostics** from the main menu.
* Click on a dashboard in the **Diagnostics** section of the navigation panel.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-b15acf5641488cddd32ee61d352e3a80ee36e843%2Falerts%20-%20Accessing%20Diagnostics.png?alt=media" alt="Accessing Diagnostics"><figcaption></figcaption></figure>

## Diagnostic dashboards <a href="#gettingstartedwithdiagnostics-diagnosticdashboards" id="gettingstartedwithdiagnostics-diagnosticdashboards"></a>

The Diagnostics dashboards contain a similar design pattern.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-b3b5a4a25c5c0484e9348ce17f9680c974584ff0%2Falerts%20-%20Execution%20crashes%20details%20page.png?alt=media" alt="Execution crashes details page"><figcaption></figcaption></figure>

### Top banner <a href="#gettingstartedwithdiagnostics-topbanner" id="gettingstartedwithdiagnostics-topbanner"></a>

The banner at the top of the page shows the summary and impact of the issue. It includes a gauge with an action menu that links to the Investigations page with more drill-down options.

### Assess issue <a href="#gettingstartedwithdiagnostics-assessissue" id="gettingstartedwithdiagnostics-assessissue"></a>

Understand the context and scope of the issue with a timeline of events and filtering capabilities by technical properties, location and organization entities.

### Troubleshoot <a href="#gettingstartedwithdiagnostics-troubleshoot" id="gettingstartedwithdiagnostics-troubleshoot"></a>

#### **Benchmarking**

Diagnostics uses anonymized cross-customer statistics from Nexthink cloud customers to help scope and troubleshoot issues. If the system does not show benchmark statistics for a given binary name, device model or version, it means that the system does not have enough statistical data to calculate it. Customers are opted-in by default to share telemetry so they can benefit from the benchmarking insights. Contact your Nexthink representative if you wish to opt out of this feature.

#### **Insights**

View automated insights that offer analysis to help find the root cause of the issue impacting devices. The algorithm uses Bayesian inference that learns from the customer's data across all devices in their environment to quantify the likelihood that a given attribute is relevant to the issue. The insight’s relevancy is based on the confidence level that is calculated using the following parameters:

* How many devices with specific property value are impacted.
* How many devices with specific property value are impacted compared to the number of impacted devices in the overall population (e.g. specific binary version vs. all binary versions).
* The frequency of the issue for the given property value.
* The frequency of the issue for the given property value compared to the frequency of the issue in the overall population.

The factors listed above affect the relevancy of a version, but do not constitute a hard threshold.

Find more information about individual pages:

* [Execution crashes](/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics/execution-crashes.md)
* [High CPU usage](/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics/high-cpu-usage.md)
* [System crashes](/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics/system-crashes.md)
* [Binary profiling](/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics/binary-profiling.md)
* [Diagnostics for alerted issues](/platform/user-guide/alerts-and-diagnostics/getting-started-with-alerts/responding-to-alerts/diagnostics-for-alerted-issues.md)
* [Additional dashboards](/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics/additional-dashboards.md)

## Embedded Diagnostics side panel in the Applications module <a href="#gettingstartedwithdiagnostics-embeddeddiagnosticssidepanelintheapplicationsmodulepageloads" id="gettingstartedwithdiagnostics-embeddeddiagnosticssidepanelintheapplicationsmodulepageloads"></a>

The system automatically enables diagnostics for the Applications module. Find them in the side panel on the Page loads and Reliability pages.

For more information, refer to the [Diagnostics section](/platform/user-guide/alerts-and-diagnostics/getting-started-with-alerts/responding-to-alerts/diagnostics-for-alerted-issues.md) of the Monitoring capabilities documentation.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-646c13df5659bc8f6d3fdc43a28fcc6413a363fb%2Falerts%20-%20Embedded%20Diagnostics%20for%20troubleshooting%20in%20Application%20Experience.png?alt=media" alt="Embedded Diagnostics for troubleshooting in Application Experience"><figcaption></figcaption></figure>

***

RELATED LINKS

* [Diagnostics for alerted issues](/platform/user-guide/alerts-and-diagnostics/getting-started-with-alerts/responding-to-alerts/diagnostics-for-alerted-issues.md)
* [Roles](/platform/user-guide/administration/account-management/roles.md)


---

# 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/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics.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.