Release LoadGen Insight Agent: 1.0.0.12962

Windows agents only: every change in this release applies to Windows agents. Linux and macOS agents are unchanged.

Agents on 1.0.0.12432 or 1.0.0.12928: these versions do not update themselves. Install this version on them by hand.

Enhancements

• New Fields on foreground_window_metric - Each foreground-window point now records how long reading the window's controls took (walk_ms), whether that read was cut short (walk_truncated), and whether the point comes from reading the window again after it came to the front (rewalk). The five-minute status line in the Insight log now also reports the median and the longest read time, with the session and process of the longest.
• Window Controls Read With a Newer Windows Interface - Two changes are visible in the controls the agent reports. The title bar and its buttons now carry automation IDs (TitleBar, SystemMenuBar, Minimize-Restore, Maximize-Restore, Close), so a launch probe that waits for one of these IDs matches every window: use an ID from the application's own content instead. And an elevated window, such as Task Manager or an administrator's PowerShell, now reports no controls and is no longer launch-timed on its title bar alone; this concerns administrators' sessions only.

Bug Fixes

• Fixed Foreground-Window Reporting Stalling Behind a Busy Window - A window that did not respond, such as Word behind its sign-in prompt, held the foreground-window helper for a minute or more, so no other window of that session was reported meanwhile, and the late window was stamped with its arrival time. Reading a window's controls is now limited in time, and every point carries the moment the window came to the front, so launch times no longer include the time spent reading the window.
• Fixed Windows Without Content at First Never Being Launch-Timed - A window that came to the front before its content existed, such as Word's start screen, was reported without controls and never launch-timed unless the user switched away and back. The helper now reads such a window again while it stays in front, for up to 30 seconds, and reports it once its controls appear.
• Fixed Quickly Closed Applications Losing Their Process - A window whose process started and stopped between two uploads, such as a quickly closed Edge window, was reported as process_name=unknown under the SYSTEM user and without a launch point. Such a window is now matched to the process that owned it when it was captured, and a window whose process cannot be named is reported under the session's user instead of SYSTEM.
• Fixed Stop Events Without a User - Stop points in process_information_metric carried no user_name, so a per-user filter on the Platform's Analysis page hid every stop. They now carry the user of the process's start.
• Fixed Data Lost When the Services Stop - Stopping or restarting LoadGen Insight, and every agent update, dropped up to 30 seconds of collected data, such as the close of an application. Insight now sends its last collection to LoadGen Control before it stops, logged as Last upload [service stop], and Control sends what it still holds before it stops.
• Fixed the Services Ending When the Host Runs Out of Memory - Under memory pressure, LoadGen Control could end on a database error while sending cached measurements, and LoadGen Insight on a failed allocation while reading performance counters. Control now logs the failure and tries again at the next interval, and Insight skips that sample with Out of memory while reading the performance counters - sample skipped in the log. Both services now log an unhandled exception before they end.
• Fixed Service Recovery Not Being Set Up - LoadGen Control looked for the services under names no current installation uses, so it configured no recovery and logged Insight service not found with any known name even when Insight was installed but failed to start. Recovery is now configured for the installed services, including a restart after a start that fails, and a failed start of Insight is logged with its reason.
• Fixed a Start of LoadGen Insight Hanging Until a Reboot - When Insight's start did not complete, for example because WMI did not answer, the service stayed in Starting until the host was rebooted. Insight now logs the step it is on while it starts, fails the start with an error after 90 seconds, and service recovery starts it again.
• Fixed Agent Updates That Could Not Start - The update script is now checked before it runs. An update whose script cannot run fails at once with the reason in the Control log and is tried again later, instead of never completing.
• Fixed a process that started and stopped within one upload staying in LoadGen Control's list of running processes, so that a later window with the same process ID was named after it
• The first start of the foreground-window helper at a Remote Desktop logon no longer logs an error while the logon is still in progress