Skip to main content

Stratora v2.4.2 Released

· 2 min read
Stratora Team

Stratora 2.4.2 is a maintenance and hardening release: in-app update awareness so you always know when a newer version is out, one-click bug reporting, refreshed and security-hardened bundled components, and more reliable installation on clean Windows Server environments.

Know when there's a new version​

Admins now see a banner and an About-page indicator the moment a newer Stratora release is available, with the release notes viewable right inside the app. No more checking a downloads page to find out you're a version behind.

Report an issue in one click​

A new Report an Issue link on the Diagnostics page opens a pre-filled GitHub issue with your version context already attached — and no identifying data. Reporting a problem is now a single click instead of a hunt for version numbers and environment details.

Current, hardened, and dependable​

  • Refreshed bundled components. PostgreSQL, NGINX, VictoriaMetrics, Telegraf, and the other bundled runtimes are updated to current stable versions — pinned, checksummed, and published as an SBOM.
  • Security hardening across authentication, licensing, secret storage, and collector configuration.
  • Reliable installation on clean or minimal Windows Server. The installer now bundles the runtime components it needs, so a fresh server installs cleanly the first time.
  • Info alert severity. A new low-severity, non-paging tier for purely informational alerts, so routine signal doesn't page anyone.

Also fixed​

  • Virtualization — accurate guest rosters (removed VMs are reaped) and corrected memory reporting for powered-off guests.
  • Alerting — reliable on-call escalation routing, clearer notification diagnostics, and no false alerts during metric-source disruptions.
  • Scope & counts — consistent site and fleet node counts, and correct site attribution for virtual machines.
  • Interface & topology — accurate port counts across switch types, topology layout fixes, and dashboard count consistency.

Upgrading: in-place upgrade from v2.4.1 (or v2.2.1). Existing monitored infrastructure is preserved.