Understanding and Aggregating ControlUp process_stops Data for Application Usage Dashboards
The discussion centers on building an Application Usage dashboard leveraging the ControlUp `process_stops` index and addresses several technical questions related to data collection, metric definitions, and field completeness.
Data from clients are collected per process exit event, with each process stop generating a record. However, data upload to the backend is batched rather than immediate, using cache files that upload roughly every 10 minutes. This means a slight delay exists between the process exit and when the data becomes available in the index. For aggregation, timestamps such as `stoptime` or `starttime` should be used as the event time, not the record creation time.
Regarding the definitions and units of key metrics like `averageworkingset_long`, `totalcputime`, or `average_user_input_delay`, no official public documentation explicitly details these metrics at field level. Users are encouraged to utilize the ControlUp AI Assistant to obtain clarifications. General ControlUp documentation may offer broader context, but precise field definitions are typically obtained through these support channels.
The `publisher_name` field may be inconsistently populated for the same process version, such as `mspaint.exe 11.2609`. This is because `publisher_name` is derived from executable file metadata or Authenticode signatures at the time the stop record is finalized. If the process terminates too quickly or the file metadata cannot be accessed—common in WindowsApps or MSIX environments—this field can be blank. Filtering results with `ispartial = false` helps ensure higher-quality data where `publisher_name` is meaningful, though blanks can be coalesced to "Unknown" or reports can group by additional identifiers like process path or file version. The `ispartial` flag indicates completeness of core stop/performance data but does not guarantee all enrichment fields like `publisher_name` or `upn` are filled.
The `upn` (User Principal Name) field, representing the user context, is also sometimes missing. This occurs when the process runs under system or service accounts, when only a username or SID is available without a UPN, or when no meaningful interactive user is associated with the process ID. This variability is expected in diverse Windows session or security contexts.
For aggregation and analysis, it is advised to use `stoptime` or `starttime` as the primary timestamps and group data by friendly process names or combinations of process name and version/path as needed. Nullable metrics such as input delay or network fields should be explicitly filtered or appropriately handled when aggregating. Multiple rows often represent distinct instances or sessions rather than duplicates.
An alternative data source, the `app_focus` index, provides per-minute records of an application's focus time and typically offers richer user identity and application name details. However, `app_focus` does not track discrete process launches as accurately as `process_stops`. Use cases focused on launch frequency benefit from the `process_stops` data, whereas `app_focus` better reflects actual user engagement duration with an application window.
Finally, a notable resolution mentioned was that the `upn` omission was fixed by updating the domain list in Employee settings, which contained only a single domain. Also, `publisher_name` is updated only once per day per process, which can affect its consistency across records. If persistent issues arise, it is advisable to open a support ticket for deeper investigation and to provide sample data for analysis.
For more details on ControlUp metrics and indexing, users can refer to the ControlUp documentation at https://docs.controlup.com and explore interactive help via the ControlUp AI Assistant. Contact ControlUp support at support@controlup.com for unresolved cases or to report suspected data enrichment issues. Read the entire article here...
