Release LoadGen Insight Agent: 1.0.0.12928

Windows agents, with one exception: every change in this release applies to Windows agents, except the System Specs Collection change, which applies to Linux and macOS agents.

New Features

• User Input Delay per Session - On Remote Desktop session hosts and multi-session Windows (Windows Server 2019 and later), the agent now measures how long user input waits before an application picks it up, per user session, and publishes it as the new user_input_delay_metric measurement: one point per session per minute with the highest and the average delay of that minute, tagged with the session's user. This supplies the input delay tile on Insight > Experience, which until now showed "Not reported by the Insight agent yet". The measurement is part of Foreground Window Monitoring, so it starts and stops with that setting and needs no extra configuration. On machines where Windows does not provide this measurement, such as single-session Windows clients, nothing is collected, and collection starts on its own if it becomes available later.

Enhancements

• System Specs Collection on Linux and macOS - Linux and macOS agents now follow the machine group's System Specs Collection setting for their system_specs host inventory: switching it off stops the inventory, and Interval (seconds) sets how often it is collected, with a minimum of 10 minutes. Until now these agents collected the inventory every 6 hours whatever the setting said. A group without the setting keeps collecting as before. Windows agents collect their inventory through the machine group's WMI queries and do not use this setting.
• Clearer Diagnostics for Foreground Window Monitoring - Every five minutes the Insight log reports how many foreground-window events arrived, so a host that sends no UX timing data stands out without debug logging. The start, end and any failure of the foreground-window helper in each user session are logged too, with the session and the reason, on lines that start with ServerAddin launcher:.
• Hardened the connection between the Insight service and the foreground-window helper in each user session: every message is validated before it is processed, and a connection that sends data the service does not accept is closed and logged as Rejected data from ServerAddin, without affecting other sessions
• The Skipping TcpConn (unknown Process ID) warning, previously written once for every affected network connection, is now a single summary line per collection pass

Bug Fixes

• Fixed Foreground Window Monitoring on Remote Desktop Session Hosts - On multi-session hosts, the helper that tracks the foreground window could not reach the Insight service from a user's session and exited immediately, so no foreground_window_metric or application_launch_metric data arrived from any session, and one failed session stopped every later session from being monitored. Each session now gets its own connection that only that session's user can open, the helper runs on the user's interactive desktop, and a problem in one session no longer affects the others.
• Fixed Insight Never Collecting After a Fresh Install - When LoadGen Insight started before LoadGen Control had received its configuration, as happens on every fresh install, it logged No configuration available yet, deferring initialization and then Config is not valid yet, will retry in 30 seconds indefinitely, and collected nothing until it was restarted by hand. Insight now finishes starting on its own as soon as the configuration arrives, and while it waits it logs where it looks for the configuration and why it cannot use it yet.
• Fixed Insight Not Reconnecting After a Restart of Insight Alone - Restarting only the LoadGen Insight service could leave it unable to reach LoadGen Control, logging Client connection is still not available after reconnect attempt. every 30 seconds and sending no data until Control was restarted as well. Control now keeps accepting new connections, so Insight reconnects on its own.
• Fixed LoadGen Control Running Its Startup Twice - Whenever LoadGen Control started with a configuration already in place, which is every start after the first, it initialized twice, so it listened for Insight twice and applied every configuration change twice. It now initializes once. Control also no longer restarts its connection listener and drops its other open connections each time Insight disconnects.
• Fixed the Insight Service Failing to Stop - Stopping or restarting a LoadGen Insight service that had not finished starting failed, and the service was left running. It now stops normally in that state. Stopping also no longer waits indefinitely for an unresponsive foreground-window helper in a user session: the helper is ended after a short wait.
• Fixed WMI Inventory Queries Returning No Rows - A WMI query with explicit properties returned no data at all as soon as one row had an empty value, for example a virtual disk without a serial number or a network adapter without a default gateway, and the agent logged Error while executing WMI query. Rows with empty values are now kept, with the empty fields left out.
• Fixed multi-value WMI properties, such as IP addresses and DNS servers, being written as the literal text System.String[]; they are now written as comma-separated values, still as text fields, so existing series keep working
• Fixed configured WMI tags being written as a type name instead of their value, which merged all rows of a query into one series; each row now gets its own series
• Fixed Insight discarding its configuration when a re-read of the configuration file failed, for example while LoadGen Control was rewriting it; it now keeps the configuration it has
• Fixed messages between the LoadGen Control and LoadGen Insight services being corrupted when they arrived in more than one piece
• Fixed Insight leaking a handle on every connection attempt while LoadGen Control was unavailable