Service Levels — branded public status page and SLA management — A new branded, public status page replaces the previous JSON-only status output. Visitors see an anonymous page showing overall and per-component status, 90-day uptime history, open incidents, and scheduled maintenance, with your own branding and component grouping. Operators get a status-page editor with an incident composer and a maintenance scheduler, plus a full SLA management area: define services, service-level objectives and policies, business hours and exclusions, record a change reason on every objective version, and set alert-rule severity as Info / Warning / Critical. Every destructive action across Service Levels now asks for confirmation first.
SessionSight live recordings — The session replay player can now play an in-progress session live and follow new activity as it streams in, so you can watch a session while it is still happening instead of only after it ends.
SessionSight AI session summaries — Generate an AI summary of a single session, or a grouped summary across a set of sessions, to speed up triage (requires the Analyse module).
SessionSight session replay player — A large batch of replay-player improvements: wider playback-speed presets, time-based rewind/forward, keyboard shortcuts with an on-screen legend, click-to-seek from the event log, in-player previous/next session navigation, an Autoplay "watch next", open-in-new-tab, and a new Inspect mode that highlights captured page elements and shows their CSS selector on hover. Replay is also more robust: seeking backwards no longer corrupts the replayed page or stalls the UI, image-mode frames load reliably, and the scrubber's event markers and idle windows stay aligned with the playhead.
SessionSight analytics — Frustration signals (rage click, dead click, quick back, excessive scroll, and JavaScript error) now appear as badges on the recordings list and can be filtered on; the Event Type filter lists the container's actual event types, including auto-derived smart events; the Heatmaps page adds new Area and Conversion heatmap types; containers gain a privacy-masking setting with Strict / Balanced / Relaxed modes; team-visible timestamped notes can be added with an in-player panel and markers on the scrubber; per-user favorites with Favorites and Unwatched tabs mark sessions watched when you open them; saved segments and ad-hoc filters can be applied to the recordings list and a funnel step can jump straight to its matching recordings; the recordings list can be exported to CSV; and a Google Analytics 4 (GA4) integration was added.
Credential Profiles — The Run-As Profiles area has been rebuilt and renamed Credential Profiles: a tabbed manager for every credential type the platform uses (Windows Run-As, Basic, SQL Login, API Key, Bearer token, Service Principal, and Azure Function key). Uptime checks, API testing authentication, and monitoring agent assignments can now reference a saved credential profile instead of holding their own inline secrets. A guided migration with a dry-run preview converts existing legacy credentials into managed profiles, and an admin is prompted to run it right after signing in. The profile picker now reliably selects a referenced profile and shows a clear, recoverable message when a referenced profile no longer exists.
API Testing — Several additions to API testing flows: paste a cURL command to create a request node; generate copy-paste CI/CD pipeline recipes for a flow; validate a response against an OpenAPI operation's schema (not just inline JSON); a per-assertion pass/fail result breakdown, with the Assertion Mode (All / Any) and assertion severity now actually applied at runtime; latency and JSONPath assertions that previously failed at runtime now run correctly; flow schedules can link alert profiles and configure retry-on-failure; and run-control actions now report errors instead of failing silently.
Uptime monitoring — Azure Function checks — Azure Function uptime checks are now modeled as two signals, HTTP availability and invocation health, shown as a 2-part result on the Test & Inspect step, the dashboard card, and the incident detail. Added support for per-function (Application Insights) checks, validation and "how to find it" help for the ARM Resource ID field, and absolute-URL validation of the endpoint so a missing https:// is caught up front.
[#9091] Added a credential-expiry Reminders hub under Uptime Monitoring. When you record a "Secret expires on" date for a Service Principal in the uptime check wizard, it appears here with a colour-coded days-left badge (Critical / Warning / OK), and the Uptime dashboard shows a banner when a credential is approaching expiry, so a client secret no longer lapses unnoticed.
[#9092] Added a collapsible "How to create the Azure App Registration for these credentials" help panel to the authentication step of the uptime check wizard (shown for Service Principal authentication), including a copy-paste PowerShell script that creates the app registration, service principal, client secret, and role assignment.
Charts — All charts across the app now render on a new in-house charting engine. This fixes charts that previously only appeared after a manual page refresh, and restores the data-point markers, entry animations, and tooltip date/time formats.
Restricted-egress / air-gapped deployments — Features that depend on internet access are now disabled or show a warning when the appliance is configured with an outbound proxy or restricted egress, instead of failing opaquely.
[#9119] Fixed the SQL Server Setup Wizard opening with the SQL Server (host/instance) field blank when editing an existing SQL datasource. It now pre-fills the saved server name (the connection string and credentials stay redacted).
[#9114] Removed leftover "LoadGen Director" references from the Settings → Configuration Options and Workloads screens; the Workloads hint now points to LoadGen Studio as the authoring tool.
[#9106] Fixed the Appliance Jobs page briefly showing an internal error placeholder (the literal text _jobsBannerError) in a red row during an Update All, which made a healthy update look like it had hung. The row now stays hidden during a normal update and only appears, with the real message, if cancelling an orchestration actually fails.
[#9109] Fixed adding a user to a Fat Client (LocalClient / TestClient) load profile not being saved: the user appeared to save but was gone on reopen and absent at runtime. Users added to classic load profiles (Fat Client, Citrix, RDP, WVD, and VMware) are now persisted correctly.
[#9111] Fixed Test Request on an Azure Function (Service Principal) uptime check failing unless you re-typed the Client Secret when editing the check. Editing a check now keeps the stored secret for the live test, and the secret fields show a "Leave blank to keep current" hint.
[#8473] Fixed the New Maintenance Window dialog defaulting and saving Start/End times in UTC instead of the appliance's configured time zone, so an operator in another zone saw times an hour off. The dialog, the maintenance list, and the page's "Times in" indicator now all use the appliance zone (set under System → Timezone; it defaults to Etc/UTC).
[#8471] Follow-up to #8473: the New Maintenance Window dialog now shows a time-zone hint beneath the Start/End fields explaining that the times are in the appliance zone and where to change it, so the default no longer reads as "one hour behind".
[#9110] Fixed two cosmetic issues in the uptime PowerShell Script editor: the Version history list showed the literal text "v@v.Version" instead of a version number, and a stray character could appear in the "use unsaved draft" helper text.
[#9107] Fixed Studio activation failing on a Linux appliance with "Access to the path '/opt/loadgen/LoadGen Studio' is denied". The unsupported on-appliance Activate this version action has been removed from the agent and Studio update cards so the failing flow is no longer reachable; downloading, uploading, and deleting versions are unchanged.
[#9103] Clarified Azure Function invocation monitoring in the uptime check wizard: it is app-wide (Azure reports invocation counts across all functions in a Function App combined, not per function), and Min Expected Invocations now defaults to 0 so an idle or low-traffic function is not flagged as failing. The live-test guidance now also lists the Client Secret, alongside the ARM Resource ID and the Monitoring Reader role, as something to verify when no invocation metrics are returned.
[#9104] Fixed the Uptime Monitoring → Reminders page showing "Tracked = 0" even after you recorded a far-future credential expiry. The count cards now reflect every recorded credential, and a new "All tracked" option lets you view long-dated reminders in the table.
[#9102] Fixed the "Validate Flow" button in the API testing flow editor appearing to do nothing when a flow had no problems. It now shows a "Flow validation passed: no issues found." confirmation.
[#9100] Fixed the API Testing Run Inspector showing a redundant inner scrollbar and very small text; the per-node timeline now scrolls with the outer panel and uses a larger, readable size.
[#9093] Fixed an Azure Function uptime check failing with "Invalid tenant id provided" even when the tenant ID was correct: the tenant ID entered in the wizard was being dropped before it reached the check. The tenant ID now reaches the check correctly and is re-populated when you edit a saved check. The same fix also restores authentication for Azure App Service checks, Azure Monitor invocation metrics, and PowerShell scripts that read the tenant ID.
[#9094] Fixed garbled characters on the SQL datasource setup card, where "Setup with wizard…" rendered as "Setup with wizard…". The wizard links and the InfluxDB token placeholder now show the correct ellipsis.
[#9036] Further fix for the SessionSight session replay player freezing at 0:00 with a stuck timeline and progress bar. The player now builds its playback timeline only from valid timestamps, so a single missing or out-of-range timestamp in a recording can no longer stall playback.
Platform and security: the application was upgraded to the .NET 10 LTS runtime, and a bundled logging component was updated to address a published security advisory.