AppPerformance
Per-application performance telemetry discovery for ACQI.
What it does
Collects per-application execution counts, CPU/memory averages, last-used timestamps, and unique-user counts to close the gap with Nexthink Application Experience. Sources, in order of preference: 1. Security Event Log 4688 (Process Creation) -- historical and user-attributed 2. WMI/CIM Win32_Process -- current process inventory and resource usage 3. Get-Process -- fallback snapshot when WMI is unavailable Output: AppPerformance.csv with columns: appName, publisher, executionCount, avgCpuMs, avgMemoryMb, lastUsed, usersAffected
How the app exposes it
The module runs through the ACQI discovery orchestrator and writes its rows into a dedicated results view. From there, conflicts, dependencies, and readiness scores feed the deal-wide consolidation layer.
/discovered/app-performance Outputs
Each module emits a normalised CSV keyed by entity ID with readiness and risk scores, evidence-source counts, and last-seen timestamps. The exact column set varies by module — the app's results view shows the live schema.