> 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/setting-up-and-managing-monitors.md). # Setting up and managing monitors Configure the **Alerts and Diagnostics** module and its content to ensure users can fully benefit from it without interruptions. * View and configure out-of-the-box monitors. See the [auto-installed system monitors](#system-and-nexthink-library-monitors) available after the module is enabled, listed on this page. * See guides on [Customizing built-in monitors](/platform/user-guide/alerts-and-diagnostics/setting-up-and-managing-monitors/customizing-built-in-monitors.md) and [Creating custom monitors](/platform/user-guide/alerts-and-diagnostics/setting-up-and-managing-monitors/creating-custom-monitors.md). * See how to [manage monitors](/platform/user-guide/alerts-and-diagnostics/setting-up-and-managing-monitors/managing-alerts.md) configured in your Nexthink instance. ## Before you begin Nexthink Administrators should enable permissions to ensure the correct configuration and monitoring of Nexthink Alerts. {% hint style="info" %} Refer to the [Roles](/platform/user-guide/administration/account-management/roles.md#roles-alerts) documentation for a detailed description of **Permissions**, **View domain** options and **Data privacy** granularity settings. {% endhint %} ## System and Nexthink Library monitors Alerts and Diagnostics module includes the following system monitors available in your Nexthink instance by default. This helps you \[problem this content resolves on a high level e.g., "track your IT environment for the most common issues" - Alerts] Find below the available system monitors. You can tailor these monitors to your preferences.
Binary performance * **Binary connection establishment time increase**: Keeps track of the average connection establishment time per binary in the last hour, for each binary present in the environment. * **Binary crashes - High percentage of devices impacted:** Keeps track of the percentage of devices with execution crashes per binary in the last 24 hours, for each binary present in the environment. * **Binary crashes increase**: Keeps track of the number of crashes per binary in the last 24 hours, for each binary present in the environment. * **Binary failed connection ratio increase**: Keeps track of the percentage of failed connections per binary in the last hour, for each binary present in the environment. * **Binary freezes - High percentage of devices with freezes**: Keeps track of the percentage of devices with freezes per binary in the last hour, for each binary present in the environment. * **Binary memory - Average memory usage increase**: Keeps track of the average memory usage per binary in the last six hours, for each binary present in the environment.
Binary - global anomalies * **Binary CPU usage - global anomaly**: Detects anomalies in CPU usage across versions or configurations of binaries, based on anonymized data from all companies using Nexthink. * **Binary crashes - global anomaly**: Detects anomalies in crashes reliability across versions or configurations of binaries, based on anonymized data from all companies using Nexthink. * **Binary freezes - global anomaly**: Detects anomalies in freezes frequency across versions or configurations of binaries, based on anonymized data from all companies using Nexthink. * **Binary memory usage - global anomaly**: Detects anomalies in memory usage across versions or configurations of binaries, based on anonymized data from all companies using Nexthink.
Binary - lagging performance * **Binary CPU usage - lagging performance**: Detects when the CPU usage of a specific binary in your organization is higher than that of other companies using the same binary. Nexthink benchmarks CPU usage with anonymized data from all companies using Nexthink. * **Binary crashes - lagging performance**: Detects when the crashes frequency of a specific binary in your organization is higher than that of other companies using the same binary. Nexthink benchmarks binary crashes with anonymized data from all companies using Nexthink. * **Binary freezes - lagging performance**: Detects when the freezes frequency of a specific binary in your organization is higher than that of other companies using the same binary. Nexthink benchmarks binary freezes with anonymized data from all companies using Nexthink. * **Binary memory usage - lagging performance**: Detects when the memory usage of a specific binary in your organization is higher than that of other companies using the same binary. Nexthink benchmarks memory usage with anonymized data from all companies using Nexthink.
Device performance decline * **Boot duration increase**: Keeps track of the average device boot duration. * **Logon duration increase**: Keeps track of the average device logon duration. * **System crashes increase:** Keeps track of the number of devices with system crashes per OS platform in the last day, for each OS platform present in the environment.
Device performance and connectivity poor ratings Detect issues based on the **poor thresholds** that Nexthink Administrators can configure for endpoint-related performance metrics of the Digital Employee Experience score. Refer to [Ratings management](https://docs.nexthink.com/platform/user-guide/administration/content-management/ratings-management#system-ratings) for more information. * **Boot speed**: Detects devices with poor *Boot duration* ratings. * **Logon speed**: Detects devices with poor *Login time* ratings. * **CPU usage**: Detects devices with frequent (30% of the time) poor *CPU usage* ratings. * **CPU interrupt usage**: Detects devices with frequent (30% of the time) poor *CPU interrupt* ratings. * **Disk queue length**: Detects devices with frequent (30% of the time) poor *Disk queue length* ratings. * **System free space**: Detects devices with poor *System drive free space* rating. * **WiFi strength**: Detects devices with frequent (30% of the time) poor *WiFi signal strength* ratings. * **GPU 1 / GPU 2 usage**: Detects devices with frequent (30% of the time) poor GPU1 or GPU2 usage rating. * **Virtual session lag**: Detects devices with poor average session network latency. * **WiFi upload speed:** Detects devices with frequent (30% of the time) poor *WiFi transmission rate* ratings. * **WiFi download speed:** Detects devices with frequent (30% of the time) poor *WiFi receive rate* ratings.
Web applications * **Web applications errors increase:** Keeps track of the increase of the number of pages with errors per web application in the last hour, for each web application defined in the Applications module. * **Web applications slow page loads increase**: Keeps track of the average page load time per web application in the last hour, for each web application defined in the Applications module. * **Web applications slow transactions increase:** Keeps track of the average transaction duration per web application in the last hour, for each web application defined in the Applications module. * **Web applications - resource errors increase**: Keeps track of the number of resource errors during past 12h, for each web application configured in your environment. * **Web applications - percentage of incomplete transactions increase**: Keeps track of the percentage of incomplete transactions during past 12h, for each transaction configured as part of web application configuration in your environment. * **Web applications - percentage of frustrating transactions per transaction increase:** Keeps track of the percentage of frustrating transactions during past 12h, for each transaction configured as part of web application configuration in your environment. * **Web applications - percentage of frustrating page loads per key page increase:** Keeps track of the percentage of frustrating page loads during past 12h, for each key page and web application configured in your environment.
Additionally, you can install and customize monitors from the [Nexthink Library](/platform/user-guide/nexthink-library.md).
Library monitors for virtual desktop infrastructure—VDI Nexthink Library offers built-in VDI-specific monitors to track real-time performance metrics and user experience in virtual desktop infrastructures. Find below some of the use cases that built-in library VDI monitors allow you to address: * Detect network congestion causing latency spikes in specific office locations. * Identify CPU bottlenecks affecting virtual desktops. * Prevent overloading of a desktop pool to maintain optimal user experience. * Identify network instability affecting session continuity. {% hint style="warning" %} Using built-in Nexthink Library VDI monitors for Alerts requires [Nexthink VDI experience](https://docs.nexthink.com/platform/user-guide/vdi-experience). {% 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/platform/user-guide/alerts-and-diagnostics/setting-up-and-managing-monitors.md?ask=&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.