Skip to main content

Changelog

All notable changes to Stratora are listed here, newest first. For detailed installation instructions see Getting Started.

v2.1.9.2 — April 23, 2026​

Bundled Components​

  • Agent 2.1.9.2 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.9.2

Fixed​

  • Escalation Teams page failed to load on tenants with rotation teams — a pgx v5 scan-plan gap caused the Escalation Teams page, alert configuration modal, onboarding wizard Alerts step, and on-call status API to error on any tenant whose escalation teams had a non-null rotation start date. Fixed at the database layer; wire format unchanged, no migration required.

v2.1.9.1 — April 20, 2026​

Bundled Components​

  • Agent 2.1.9.1 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.9.1

Fixed​

  • Agent auto-enrollment uses the server's configured FQDN. Agents deployed from the agent install page and collectors deployed from the collector install modal now consistently use the server's configured FQDN for their connection URL, matching the setup wizard's Deploy Agents step. Administrators accessing the server UI from different URLs (by hostname, IP, or FQDN) will always get the correct install command.
  • Collector failover correctly identifies the local collector. On first startup after upgrade, the server flags its bundled local collector as the fallback target for the collector failover mechanism, so sites whose preferred collector becomes unreachable will automatically fail over to the local collector as designed.
  • Node detail view reflects current collector assignment. The node edit dialog and node detail pages now consistently display the currently-assigned collector for each node.

Operator Notes​

  • In-place MSI upgrade from v2.1.9 or earlier. No database migration required.
  • Agents stuck in a Disconnected state from a v2.1.9 install that used the wrong server URL can be re-enrolled by re-running the MSI install from the agents page.

v2.1.9 — April 19, 2026​

Bundled Components​

  • Agent 2.1.9 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.9

Fixed​

  • Tray indicator starts automatically for all users. The Stratora tray indicator now launches for every interactive Windows user at logon after agent or collector installation, using a per-machine startup registration. Previous releases used a single-user registration path that left the indicator invisible on multi-admin servers.
  • Orphan registry values cleaned up on upgrade. Upgrading from a prior release automatically removes the leftover registry values created by the previous single-user registration path.
  • Single-instance guard on the tray indicator. If a host carries a legacy per-user auto-start entry alongside the new per-machine entry during the upgrade window, the tray indicator deduplicates within a logon session so users see exactly one icon.

Operator Notes​

  • In-place MSI upgrade from v2.1.8 or earlier. Users will see the tray indicator on their next logon.
  • The -install-startup and -uninstall-startup flags have been removed from stratora-tray.exe; auto-start registration is handled by the MSI installer. Remove any scripted invocations of those flags.

v2.1.8 — April 17, 2026​

Bundled Components​

  • Agent 2.1.6 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.6

Fixed​

  • Topology auto-map now tracks the site's live node set. Node deletions, rejections, deactivations, and cross-site moves previously left orphan elements on the map; reconcile now adds missing elements AND prunes orphans in a single pass.
  • Three additional node-creation paths now fire the auto-gen hook chain: discovery single import, discovery bulk import, and agent self-enrollment. Before 2.1.8, bulk-importing discovered devices into a fresh site produced no topology map.
  • DeleteNode and RejectNode fire the topology hook. Cross-site moves explicitly prune the old-site map.

Changed​

  • Migration 151: topology_maps.site_id FK changed from ON DELETE SET NULL to ON DELETE CASCADE. One-shot cleanup of auto-generated orphans included; user-created maps preserved.
  • BackfillAllSites at startup reconciles every site with nodes. First 2.1.8 boot cleans element drift accumulated under the previous additive-only semantics.

Operator Notes​

  • First boot of 2.1.8 will clean accumulated orphan elements from auto-generated maps. User-edited maps are not touched.
  • Schema migration 151 runs automatically on first 2.1.8 startup. No manual DB intervention required.

v2.1.7 — April 17, 2026​

Bundled Components​

  • Agent 2.1.6 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.6

Fixed​

  • Auto-generated topology map is now created and linked to the Network Topology panel on fresh deploys, wizard completion, and first-node-add. Previously the panel rendered "No map selected" because BootstrapDefaultSite bypassed the auto-gen hooks and per-request hooks raced the dashboard regeneration against the map creation.
  • BootstrapDefaultSite now fires the same sequenced auto-gen hooks as SiteHandler.CreateSite, so the default site starts with a dashboard and picks up its topology map as soon as the first node arrives.
  • Site/node hook call sites (CreateSite, CreateNode, UpdateNode, ApproveNode, bulk node move) now run topology regeneration before dashboard regeneration inside a single goroutine, eliminating the race that could leave mapId stored as empty permanently.
  • Dashboard read path self-heals empty mapId values on auto-generated site topology panels by resolving the live map at response time. Repairs dashboards already persisted with empty mapId from earlier builds; no migration required.

Changed​

  • Auto-generated topology map IDs are now deterministic UUID v5 values derived from the site ID. Deleting and regenerating the auto-map reuses the original ID, so dashboards referencing the old ID survive the cycle. Differs from prior releases where regenerated maps received a fresh random UUID.

v2.1.6 — April 16, 2026​

Bundled Components​

  • Agent 2.1.6 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.6

Added​

  • Node stabilization lifecycle -- newly-created nodes receive a 5-minute stabilization window during which alert evaluation is skipped and the node is excluded from the system-wide health score. Prevents false alerts and health score dips immediately after discovery imports or agent enrollment.
  • "Agent Not Reporting" alert -- fires when an agent node completes stabilization but has never checked in. Resolves automatically when the first heartbeat arrives.
  • Audit log events for node stabilization lifecycle (node.stabilization_started, node.stabilization_completed).
  • "Stabilizing" visual state in node list, node detail, site nodes, topology maps, and dashboard panels.

Changed​

  • Replaced 4 copy-pasted grace period blocks in the alert evaluator with a single IsNodeStabilizing() helper driven by the stabilization_until timestamp.
  • Server MSI now supports in-place upgrades. PostInstall.ps1 detects upgrade scenarios and preserves database credentials, SSL certificates, and service registrations.
  • Added PreInstall custom action and WiX ServiceControl elements to stop services before binary replacement during upgrade.
  • Migration 059 (legacy collector migration) guarded for fresh installs without legacy collectors table.

Known Issues​

  • Users upgrading from v2.1.5 may see a files-in-use dialog during installation. Click OK to continue -- no reboot is required. This dialog will not appear on future upgrades (v2.1.6+).

v2.1.5 — April 15, 2026​

Bundled Components​

  • Agent 2.1.5 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.5

Fixed​

  • Device templates installed to wrong path on fresh deployments — WiX heat.exe was invoked with -srd (suppress root directory), which dropped the templates intermediate directory and placed YAML files at config\devices\ instead of config\templates\devices\. All template lookups failed, producing zero SNMP input blocks for 10/12 node types. Removed -srd so the install path matches the Go backend's default.
  • SNMP fallback path defaulted community string to "public" instead of reading the node's assigned credential from the encrypted store. Nodes without a matching device template now resolve their credential via the same decryption path as template-based nodes.

v2.1.4 — April 15, 2026​

Bundled Components​

  • Agent 2.1.4 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.4

Fixed​

  • Setup page (/setup) hung on "Getting things ready..." indefinitely due to CSP violation — the inline polling script was blocked by NGINX's script-src 'self' policy. Extracted the IIFE into an embedded setup.js file served via a new /setup.js route; the auto-redirect to /login after service initialization now works correctly on fresh installs.

v2.1.3 — April 15, 2026​

Bundled Components​

  • Agent 2.1.3 (Windows)
  • Agent 1.2.1 (Linux)
  • Collector 2.1.3

Audit Logging​

  • Full CRUD audit coverage across collectors, site photos, contact bulk import, OIDC provider config, component enrollment, server startup, and migration application events.
  • Self-service password change and session cleanup events.
  • IdP contact sync events (create, update, merge) with system actor attribution.
  • License parse-failure downgrade events.
  • DB-level soft immutability via trigger (migration 146) — direct mutation of audit_logs raises an error; retention managed via SECURITY DEFINER function only.

Escalation Teams​

  • Contact references stored in escalation_channel_contacts junction table (migration 144); email/Slack/Teams dispatch resolves contacts from junction.
  • Live on-call preview banner in rotation schedule showing current position holder and next shift handoff time.
  • Drag-and-drop reordering for rotation members (with keyboard-accessible fallback).
  • Save-time configuration warnings when rotation members lack phone/email for targeted channels.
  • Dispatch-time audit log entries when SMS/Voice notifications are skipped due to missing phone numbers.
  • SMS/Voice targeting chips (On-Call #1, All Members, Specific Contacts) now fully honored by backend dispatch.
  • oncall_notify_sms / oncall_notify_voice toggles exposed in UI for rotation teams.
  • Slack/Teams channels now support ContactPicker for individual contacts alongside freeform webhook URLs.

Contact Registry​

  • IdP sync merge path — existing manual contacts promoted to managed on email match at login.
  • Bulk import now logs aggregate audit entry with imported/merged/skipped/errors counts.
  • Two-step modal redesign (Basic Info → Notification Channels).
  • Phone number normalization via react-phone-number-input (country code enforcement, auto-formatting).
  • ContactPicker filters to only show contacts with the required channel configured.

Fixes​

  • User menu dropdown clipped by overflow-hidden on TopNavBar flex container.
  • UpsertContactFromIdP: email no longer NULL on fresh IdP contact creation.
  • Toast regressions: acknowledged alerts no longer re-appear; dismissing via "View" works correctly; tab sleep/wake no longer causes burst toasts; toasts no longer render above modals.
  • Escalation teams: clone preserves junction-backed ContactIDs; ConfirmDialog renders via createPortal; SMS/Voice dispatch respects target_type and oncall_position_offset; delete of in-use teams succeeds.

Changed​

  • escalation_step_channels.contact_ids column dropped (migration 144); replaced by junction table.
  • contacts.external_id partial unique index added (migration 145).
  • Alert toast polling: acknowledged alerts excluded from recent alerts endpoint.
  • Escalation rotation-member SMS/Voice dispatch gated on oncall_notify_sms / oncall_notify_voice flags (migration 147).
  • All components (Server, Agent, Collector) versioned in lockstep at 2.1.3.

v2.1.1 — April 6, 2026​

New Built-In Reports​

  • Alert Intelligence (7-day and 30-day) — severity breakdown, top noisy nodes, time-to-acknowledge and time-to-resolve metrics.
  • Availability / SLA (monthly and quarterly) — per-site uptime percentage, downtime, incident count, MTTR, MTBF.
  • Top Offenders (24-hour and 7-day) — top nodes by CPU, memory, latency, interface errors.

Linux CPU and Memory Alerts​

Built-in alert definitions for Linux nodes added: High CPU Usage (warn 80%, crit 95%) and High Memory Usage (warn 80%, crit 95%) with a 5-minute sustain window. Evaluator queries linux_cpu_usage_percent and linux_memory_usage_percent scoped to linux-server nodes only.

Windows and Linux memory alert warning thresholds lowered from 85% to 80% in built-in definitions.

Fixes​

  • NGINX reload (FQDN save, cert upload, ACME issuance, manual reload) no longer causes a 5-second HTTPS outage — service restart now runs asynchronously after the HTTP response is sent.
  • Setup wizard step 3 now shows an error toast when the FQDN save fails on a network error instead of silently stalling.
  • Top Resources widget no longer returns 500 — removed invalid deleted_at column reference from GetFreshNodeIDs; canonical is_active = true filter is sufficient.
  • Discovery jobs stuck in running state after a server crash or unclean shutdown are now automatically recovered at startup and marked failed with a descriptive error.
  • Discovery scan context now has a 1-hour maximum runtime deadline; scans that hang indefinitely are cancelled and marked failed.
  • Collector Failover alert definition no longer fires false positives against non-collector nodes when they go offline — now correctly routed to the collector-scoped evaluator.
  • Alert toast ACK/Escalate buttons now show "Alert already resolved" instead of a generic error when the alert resolved before the user could act.

v2.1.0 — April 1, 2026​

Disk Capacity Reporting​

New PDF report type showing disk usage trends across monitored nodes with projected full dates via linear regression. Available in the Reports engine with Run Now and scheduled delivery.

Site Photos​

Upload and manage photos for each site — equipment, rack layouts, floor plans. Photos are stored securely, served with authentication, and viewable in a lightbox gallery on the site detail page.

Site Detail Page​

Each site now has a dedicated page with eight tabs: Overview, Dashboard, Nodes, Topology, Racks, Alerts, Reports, and Photos. The Overview tab shows node health, device breakdown, and IPAM networks. An attention strip surfaces degraded, critical, and offline nodes at a glance.

Node Quick Filters​

The Nodes tab includes filter toggles (All / Warning / Critical / Offline / Healthy) with live counts, letting you focus on problem nodes without leaving the site context.

About Page​

Settings → About now shows the running platform version, build information, and open source component attribution.

Bug Fixes & Polish​

  • Platform version now correctly reported across all API endpoints
  • Homepage layout streamlined — cleaner health ring, reordered right rail, reactive accent bar and ambient glow reflecting node health state
  • Report template names normalized