Release LoadGen Api, Appliance and MCP Server: 1.0.0.11809

Release LoadGen Api, Appliance and MCP Server: 1.0.0.11809

LoadGen General

  • No general changes in this release.

LoadGen Api

  • Per-Service-Type Capability Registry for Uptime Checks : Each uptime service type now declares which signals it actually produces (such as status code, response body, SSL certificate, SQL result, banner, round-trip time) and which form fields apply. Alert profiles automatically skip conditions that target signals a check cannot produce (with a debounced log line per check), so a status_code != 200 condition no longer fires every tick on an SSH check. The catalog response now includes a signals array and applicableFields list per entry so the frontend can render type-specific form fields. Create, update, and Test endpoints return wrapper responses that include a nonApplicableFieldsConfigured warning list so operators can clean up checks that have HTTP fields populated on non-HTTP types.
  • Fixed the uptime catalog signals field still being serialized as an integer bitmask instead of an array of names, which had crashed the frontend check-type wizard with a deserialization error.
  • Fixed the uptime Analytics drawer trend chart silently appearing empty even though the summary cards showed real data, due to a CRLF parsing issue in the InfluxDB CSV response.
  • Fixed GET /v1/uptime/groups returning 404 (which broke the new check-type wizard's catalog tree) and the master-mode "list syncable entity types" endpoint having the same defect; both routes now resolve as documented in the Swagger and frontend specs.

LoadGen Appliance

  • No Appliance changes in this release.

LoadGen MCP Server

  • No MCP Server changes in this release.
Was this article helpful?
0 out of 0 found this helpful