High CPU usage
Last updated
Last updated
Assess and troubleshoot issues related to binaries with high CPU usage.
Nexthink continually optimizes its functionalities to better serve customer needs. As a result, the High CPU usage dashboard is being phased out in favor of more tailored features and is no longer developed or enabled for new customers. For further details on new features, refer to the Understanding cloud insights documentation.
Select Alerts and Diagnostics from the main menu.
Click on High CPU usage from the navigation panel. The page lists binaries with high CPU usage in the last 72h.
You can search and sort the table to focus on specific issues.
The Binaries with high CPU usage table is organized by:
Binary name: Click on the binary name to access the High CPU usage details page with troubleshooting options for a given binary.
Product name: The name of the product that matches what appears in the binary inventory. If the same binary name has multiple entries, Nexthink chooses the most common one.
User interface: This column indicates if the binary has a user interface (UI). Note that certain binaries that run in the background may have configuration UI. If this is the case, a yes will appear for them in this column but only if the binary runs on a Microsoft Windows operating system.
# devices with issues: The absolute number of devices that had at least 1 high CPU event in the past 7 days.
Execution events with high CPU: The absolute number of execution events that had high CPU usage.
% of devices with issues: The percentage of devices with issues.
Currently, Nexthink enables this feature for customers with fewer than 20,000 endpoints as we are fine-tuning performance improvements.
The top banner shows the number of devices that experienced high CPU execution events at least once in the last 72 hours. It lists the affected binary, product name and whether there is a user interface.
The devices link in the summary directs you to the Investigations dashboard for more information about impacted devices.
High CPU threshold: Define the percentage of CPU used by the binary over a 15-minute period for it to be considered as high CPU usage. The default value is 5%.
Devices with issues: Shows the number of impacted devices.
Understand the context and scope of the binaries with high CPU usage:
Execution events with high CPU: View high CPU execution events over a given time period. Use the timeframe picker in the upper-right corner to change the time period.
Hierarchy: Filter results by hierarchy levels in your organization. This option is available only for users of hierarchies (classic).
Location: Filter results by geolocation hierarchy. This section is visible only if the Geolocation feature is enabled. You can configure it on the Product configuration page of the Administration module.
Technical: Filter results by technical criteria such as Operating System and Platform.
Automated insights automatically check which binary versions are relevant for finding the root cause of the issue. The AI-based judgment provides results marked with red color for values most relevant to the issue.
Version: View the version of the binary.
Execution events with high CPU: View the absolute number of executions marked as high CPU usage over a 15-minute period, based on the threshold selected from the dropdown menu at the top of the page.
Devices with issue: View the absolute number of devices where high CPU usage was observed for the binary. A device is considered to have an issue when at least once, within the defined timeframe, the binary had high CPU usage. The percentage is calculated only for the given property value.
RELATED LINKS
