📜Talon 3.16.72
Release Date: Wednesday, May 27, 2026
Compatibility Notes
The following issues have compatibility implications:
Change Summary
Bugs
TALON-159
Heartbeat SrvMonSysMemoryStats.processRssBytes XML id collides with Rumi 4.0 schema (breaks rumi-agent deserialization)
Prior to this release, an XML field id collision in the heartbeat schema between nvx-talon 3.16.70 and Rumi 4.0 caused the Rumi management agent to throw {{IllegalStateException: field type mismatch (exp=0x02, actual=0) for field 26}} when deserializing heartbeats from any XVM running 3.16.70, dropping every per-XVM metric from the management dashboard. In nvx-talon 3.16.70, the {{processRssBytes}} implementation in {{SrvMonSysMemoryStats}} was assigned an XML id that Rumi 4.0 had already allocated to an unrelated embedded-entity field. This release places {{processRssBytes}} at the XML id Rumi 4.0 uses for the same field, so the rumi-agent decodes it correctly. Existing rumi-agent installations resume processing heartbeats without modification once XVMs are upgraded to this patch; heartbeats are transient telemetry, so no data migration is required.
Compatibility Notes
Areas of Impact: Management / monitoring (heartbeat metrics)
Action required for customers on nvx-talon 3.16.70. This patch must be installed on every XVM running 3.16.70 to restore heartbeat metrics. Without it, the rumi-agent (2.0.x, compiled against the Rumi 4.0 schema) cannot deserialize heartbeats from those XVMs and every per-XVM metric stays absent from the management dashboard. Customers on 3.16.63 or earlier are unaffected.
Wire-format change. The on-wire field id for {{processRssBytes}} in 3.16 changes from 26 to 34. Heartbeats are emitted 1:1 from each XVM to the rumi-agent, so there is no mixed-version concern across a fleet; the {{processRssBytes}} metric starts to appear in management dashboards for each XVM independently as that XVM is upgraded to the patched build.
Heartbeat log replay. Heartbeats captured by an unpatched 3.16.70 XVM into a heartbeat log cannot be replayed using {{hbcollect.sh}} against a 2.0.x rumi-agent, because the same wire-id 26 type mismatch that breaks live ingest also breaks log replay. Logs captured from patched XVMs onwards replay normally. There is no backfill path for the coverage gap between 3.16.70 going out and this patch being installed.
Last updated