Data-model changes

Contents

Data-model changes

CPU of each execution

Starting from this release, Engine will store the CPU consumed by each program execution. The corresponding data can be extracted using the two following aggregates that apply to:

  • Users
  • Devices
  • Applications
  • Executables
  • Binaries
Field Group Type Windows black.png Mac black.png Mobile black.png
Total CPU time Activity Aggregate Windows black.png Mac gray disabled.png Mobile gray disabled.png
Indicates the sum of the CPU time of all executions on each device in scope and over all logical processors.
  • Example: if we consider two executions with the first one taking 50% of a logical processor during 30 minutes and the second one taking 100% of 2 logical processors during 60 minutes, the total CPU time is 135 minutes (= 50% * 30 min + 2 * 100% * 60 min).
CPU usage ratio Activity Aggregate Windows black.png Mac gray disabled.png Mobile gray disabled.png
Indicates the sum of the CPU time of all executions on each device in scope over all logical processors divided

by their total duration.

  • Example: if we consider two executions with the first one taking 50% of a logical processor during 30 minutes and the second one taking 100% of 2 logical processors during 60 minutes, the CPU usage ratio is 150% (= [50% * 30 min + 2 * 100% * 60 min] / [30 min + 60 min]).

Moreover this data is also available in execution events:

Field Group Type Windows black.png Mac black.png Mobile black.png
Total CPU time Activity Aggregate Windows black.png Mac gray disabled.png Mobile gray disabled.png
Indicates the sum of the CPU time of all executions on each device in scope and over all logical processors.
  • Example: if we consider two executions with the first one taking 50% of a logical processor during 30 minutes and the second one taking 100% of 2 logical processors during 60 minutes, the total CPU time is 135 minutes (= 50% * 30 min + 2 * 100% * 60 min).

Memory of each execution

Starting from this release, Engine will store the memory consumed by each program execution. The corresponding data can be extracted using the following aggregates that applies to:

  • Executables
  • Binaries
Field Group Type Windows black.png Mac black.png Mobile black.png
Average memory usage per execution Activity Aggregate Windows black.png Mac gray disabled.png Mobile gray disabled.png
Indicates the average memory usage of all underlying executions before aggregation. The value is the average

memory usage of all executions (calculated with a 5-minute resolution) multiplied by their cardinalities and divided by the total cardinality.

  • Example: if two tabs of the Chrome browser are opened at the same time, two distinct processes of chrome.exe are launched and they are aggregated by the Engine (i.e., event cardinality = 2). The average memory usage will be the average of the two processes before aggregation: it represents the average memory usage of a Chrome tab.

Moreover this data is also available in execution events:

Field Group Type Windows black.png Mac black.png Mobile black.png
Average memory usage Properties Field Windows black.png Mac gray disabled.png Mobile gray disabled.png
Indicates the average memory usage of the underlying executions before aggregation with a sampling resolution of 5 minutes.
  • Example: if two tabs of the Chrome browser are opened at the same time, two distinct processes of chrome.exe are launched and they are aggregated by the Engine (i.e., event cardinality = 2). The average memory usage will be the average of the two processes before aggregation: it represents the average memory usage of a single Chrome tab.

New field

The following field has been added:

Field Group Type Windows black.png Mac black.png Mobile black.png
Hard disks manufacturers Local drives Field Windows black.png Mac black.png Mobile gray disabled.png
Indicates the list of hard disk manufacturers

Changes in packages

Starting from Nexthink V6.3, those investigations retrieving packages or including a condition on packages have been simplified. The results take into account only those packages that are effectively installed, discarding uninstalled packages.

Find out more

Deprecated fields

The following fields of Binary have been deprecated in favor of the more expressive aggregates presented above:

  • Average CPU usage
  • Average memory usage
Retrieved from "https://doc.nexthink.com/Documentation/Nexthink/latest/ProductOverview/Data-modelchangesinV6.3"