Skip to main content

Stratora v2.4.4 Released

· 3 min read
Stratora Team

Stratora 2.4.4 adds out-of-band server monitoring for Dell iDRAC and HPE iLO, publishes a per-device compatibility matrix, and ships five new network and environmental alerts — alongside consistency and correctness fixes across memory reporting, the alert builder, and dashboards.

Out-of-band server monitoring​

Monitor Dell iDRAC and HPE iLO service processors over SNMP — server health without an agent on the host or access to the OS. A new Out-of-Band Management device category auto-recognizes iDRAC and iLO controllers and builds a full dashboard: overall health rollup, temperature probes (each named by its location — inlet, exhaust, CPU), fans, power supplies and PSU redundancy, physical disks/RAID, and memory modules.

Environmental alerting ships as built-in alerts keyed on the controller's own health status (normal / fault), not user-set thresholds — the BMC reports each sensor's own good/bad state, so there is no custom temperature threshold to set on BMC readings, and BMC alerts are not built through the custom alert picker.

Monitoring is over SNMP only. IPMI is a deliberate exclusion for security reasons; Redfish support is on the roadmap.

A device compatibility matrix​

The Supported Devices page now states, per device, how far each template has been validated — real hardware, real-capture replay, or MIB-derived. It is the authoritative answer to "is my device supported, and how confirmed is it": a MIB-derived template was built from vendor documentation and not yet confirmed against physical equipment. Check it before relying on a device class in production.

New built-in alerts​

Five network and environmental alerts ship enabled and name the affected component, not just the node: Network Device CPU High (SNMP switches, firewalls, access points), Access Point Memory High (worst AP in an Aruba Instant cluster), Disk High Temperature (hottest NAS disk), and PSU / Fan Failure and Fan Stopped (Synology and QNAP chassis sensors). They fire only on device families validated for each metric; unvalidated families don't fire and are labeled as such rather than showing empty charts.

Action required — re-check memory alert thresholds​

Memory readings are now consistent across platforms: every memory surface computes physical RAM in use — (total minus available) over total — on Windows and Linux alike. Thresholds are unchanged; only the underlying reading moved, and it moved in opposite directions by platform:

  • Linux readings are now higher. The previous figure understated true usage on some distributions (Debian by ~6 points, Ubuntu by ~7). A Linux node sitting just under a threshold can now cross it on upgrade with no config change — an alert you didn't have before.
  • Windows readings are now lower. The previous figure overstated usage by 5–18 points, so some nodes move from Critical to Warning.

Re-check your memory alert thresholds after upgrading, on both platforms.

Also in this release​

  • Every metric in the custom alert builder now resolves to a live query — options that never fired are gone or repointed, with clearer names; existing alerts are migrated where unambiguous.
  • Storage RAID and BMC status read in words (e.g. "Fault", "Redundant") instead of raw numbers.
  • Merging dashboard panels is more predictable — combined panels resolve live, and a panel whose source has no data says so instead of vanishing.
  • Interface Utilization is now available on access points, firewalls, ESXi hosts, and NAS devices.

Upgrading​

Download the 2.4.4 server installer and run it on your Stratora server. It is an in-place upgrade — existing monitored infrastructure, dashboards, and settings are preserved.

Bundled Components​

  • Agent 2.4.4 (Windows)
  • Agent 2.4.4 (Linux)
  • Collector 2.4.4
  • PostgreSQL 17.10
  • VictoriaMetrics 1.147.0
  • NGINX 1.30.4
  • Telegraf 1.39.1