Release LoadGen Api, Appliance and MCP Server: 1.0.0.11981

LoadGen General

• No general changes in this release.

LoadGen Api

• [#8511] Fixed first-time users being unable to create a monitoring profile: with zero workloads on the appliance, saving failed with "A workload file must be selected for each agent assignment.", while a workload can only be authored in LoadGen Studio against an existing profile (a chicken-and-egg). A monitoring profile can now be saved disabled without any workload, so you can author the workload in Studio afterwards and connect it. Enabling a profile still requires a workload per agent assignment, and that rule now also guards the enable action itself, which previously allowed switching on a workload-less profile into a state that silently did nothing at the next monitoring run.
• [#9036] Fixed the SessionSight dashboard under-reporting activity: the Event Distribution donut showed only a tiny slice (e.g. "mutation: 5") while the Events KPI counted tens of thousands, because no period-wide event breakdown existed and the chart fell back to the realtime data. The analytics overview now includes a period-wide breakdown per event type (count and share, largest first) that sums to the Events KPI by construction, so the chart and the KPI agree. Events without a type are counted as unknown instead of being dropped.
• [#9037] Fixed the SessionSight Visitors list and visitor-detail pages hanging for ~30 seconds and rendering blank. Opening a single visitor no longer scans every visitor in the container: the lookup is filtered to the requested visitor, the default reporting window is reduced from 90 to 30 days (explicit start/end dates still allow longer ranges), and a query that still runs long is now cut off after 25 seconds with a clear 504 error instead of a silent timeout. The underlying daily visitor rollup is also stored far more compactly, and existing history self-heals through a one-time automatic recompute on upgrade.
• [#9038] Fixed the SessionSight Heatmaps page hanging for ~30 seconds and never rendering the page image behind the heatmap overlay. The lookup that picks a captured session to use as the background image scanned the entire history; it is now bounded to the container's configured retention period (default 90 days), since older sessions have already been purged and can never yield a usable snapshot.
• Phantom "Citrix" load profile. Fixed Testing → Load Profiles showing a ghost entry (no name, a Citrix technology tag, 0 workloads, an Activate button) on appliances with no real testing profiles configured. An internal migration marker stored alongside the profiles was being read as if it were a profile; the profile reader now skips it and also ignores any nameless, unusable entries. Fully backward-compatible: no action is needed on existing appliances.

LoadGen Appliance

• Azure VM readiness. The appliance now behaves correctly when deployed as an Azure VM, on both fresh images and the already-deployed fleet. Disk extend (Infrastructure → Appliance → Extend disk) no longer depends on luck for its growpart tooling: fresh images now ship the cloud-guest-utils package, and existing appliances self-heal by installing it on the spot if a disk extend finds it missing (previously a resize could silently stop short on images that lacked it). In addition, the Azure Linux agent (walinuxagent) is installed and enabled automatically at appliance startup when running on Azure, and only on Azure: on Hyper-V, VMware and VirtualBox this is a no-op, so on-prem images stay clean.

LoadGen MCP Server

• No MCP Server changes in this release.