Release LoadGen Api, Appliance and MCP Server: 1.0.0.12115
Release LoadGen Api, Appliance and MCP Server: 1.0.0.12115
LoadGen General
Important — do not deploy this build (dead on arrival). The API in 1.0.0.12115 fails to start due to a startup crash found immediately after release, so this build is effectively dead on arrival. It is superseded by 1.0.0.12121, which fixes the startup issue. On-premises installations should use 1.0.0.12121 or later. The changes below are listed for completeness and all ship in 1.0.0.12121 and later.
LoadGen Api
Credential Profiles — platform-issued agent tokens and keys are now recorded. Tokens and keys that the platform issues once and previously kept only as a hash are now saved as Credential Profiles, so you can see and manage them alongside your other platform keys: Core Agent Appliance enrollment tokens and per-appliance keys, Insight enrollment tokens, group keys and per-machine keys, cloud monitoring agent keys, and repository sync keys. Recording is best-effort and never puts a minted token at risk; the profile list shows presence only (there is no reveal for any profile type), and the raw value is still shown once at creation.
[#9187] Fixed VDI Agents always showing Offline because the platform probed the wrong management port. VDI Agents use the same management port as Full Agents (4840); a one-time migration moves existing VDI agent bindings to 4840 so they come back Online without being re-added. Requires an API redeploy.
[#9187] Added an agent reachability preflight so you can tell why an agent shows Offline. A new POST /v1/agents/reachability endpoint — and a Test connection button in the Add/Edit agent dialogs — opens a TCP connection to a given host and port and classifies the result (Connected, Refused, Timed out, Unreachable or DNS failed) with an operator hint. It takes a host and port rather than an agent id, so you can test a connection before the agent exists as well as after.
[#9206] Fixed a manually started Core/Web load test hanging indefinitely in "Starting users — ramping up…" with 0 agent slots when the Core Agent never connected back. The run now fails fast (within about 90 seconds) with an actionable message — no Core Agent connected back to the results listener on port 4851; verify the callback address is routable and the agent is online — instead of sitting in ramp-up until you cancel it.
[#9205] Fixed SessionSight replay returning a generic "…status 500" when its datastore was briefly unavailable. A transient datastore outage now returns a typed 503 (and a 504 on timeout) across every SessionSight endpoint, so the UI can show an accurate temporary-unavailability message. Recovering the datastore itself remains an infrastructure task.
Request logging — accurate status codes. Fixed request-log lines recording 200 for endpoints that actually returned a non-200 result (for example a 504 agent-offline probe), so scanning the request log or its metrics for errors now shows the true status.
LoadGen Appliance
[#9209] Fixed the Let's Encrypt HTTPS wizard restarting the frontend a second time when activating a certificate, which briefly dropped the session and produced an unexplained "Connection Lost — Could not reconnect — reloading" prompt after the certificate had already been issued. Activating a Let's Encrypt certificate now applies without bouncing the running frontend; other certificate modes keep their existing behaviour. The certificate itself always issued correctly — this removes the disjointed reconnect.
LoadGen Core Agent Appliance
On-box agent and console improvements. Following first field testing, the appliance's on-box agent and boot console gained several fixes: console-entered settings (the Platform URL, enrollment token and trust flag) now persist across an Appliance Agent restart; the appliance reports the Core Agent version reliably; and Platform URL entry is validated (a valid http/https URL) with clear error messages.
Trust a self-signed Platform certificate (opt-in). An appliance can now register against a Platform that presents a local or self-signed certificate, via an opt-in trust option on the console. Valid certificate chains are always required to pass; the setting applies to the outbound Platform connection only and takes effect without restarting the agent.
Expanded login menu. The boot console's interactive menu gained options to register with the Platform now, trust a self-signed Platform certificate, change the hostname, set a static IP (with a 60-second confirm-or-rollback) and set or clear DNS. You can reopen the menu at any time with loadgen-console.