Understanding cloud insights

Nexthink detects binary issues and determines their root causes by leveraging cross-customer data. The system reports issues on the Alerts overview page as system alerts with the Cloud insight label and on the Binary profiling dashboard as right-side panel Insights.

Binary configuration

The system detects abnormal binary performance metrics across all organizations using Nexthink, taking into consideration the binary version and operating system version. A binary name, along with its version or the operating system versions (or both), is referred to as binary configuration. For example, the following are binaries configurations:

  • version of zoom.exe.

  • version of zoom.exe running on Windows 10 Enterprise 21H2 (64 bits) - version 19044.3324.0.0.

Binary insights types

There are two types of Binary insights we provide today:

  • Insights on global issues: Detect global binary issues related to the specific binary configuration's worse performance compared to other configurations. This issue is visible across many customers and may be vendor-related.

  • Insights by benchmarking: Compare binary performance with other organizations to identify areas with significant performance differences. These issues are related to the local customer setup, not the vendor.

How does Nexthink generate insights?

This section explains how Nexthink detects and determines binary issues.

  • The system uses the organization's data from the past 7 days and anonymized statistics from other organizations using Nexthink from the past 4 weeks to compute insights.

  • The system uses absolute thresholds to evaluate binary configurations individually based on the four performance metrics:

    • Normalized CPU usage: The CPU's capacity a binary used, calculated by looking at how much CPU time it consumed compared to how long it was running.

    • Memory usage: The average memory usage of the specific binary configuration for the given timeframe.

    • Freezes: The frequency of freezes that occur concerning the execution duration. The system displays the value in hours.

    • Crashes: The frequency of crashes that occur concerning the execution duration. The system displays the value in hours.

  • The system computes performance metrics for binary insights using the median, while various reports across the product (such as Binary profiling) usually compute the average.

  • Nexthink identifies the impact for your organization based on the number of devices with the specific binary configuration.

  • A specific binary configuration must be observed on at least 500 devices across five different customers to be evaluated.

  • During issue detection, Nexthink sets thresholds on different levels of configuration details. For example, it compares the performance of a specific binary version running on a specific operating system with the overall performance of this binary version.


Last updated