Log Forwarder Release Notes
Linux and macOS log forwarders can update themselves once you turn on Auto-upgrade under Configure → Log Forwarders. Windows forwarders are updated by reinstalling with the newer bundle. See Updates for the full picture of how delivery works and how to stay in control of when it happens.
Every published release is listed here, newest first. Entries are added as releases ship and are never removed, so this page is the running record from here on. It begins with the five most recent releases as of the day it was written; anything older predates the page.
For a tour of what GridNMS can do today, grouped by capability rather than by release, see What’s New.
0.69 — November 2, 2026
Section titled “0.69 — November 2, 2026”-
A forwarder that looked for an update at the wrong moment no longer stops looking for six hours. When a new version is made available, the collector a forwarder reports to prepares each piece of the update in turn, which takes a few seconds. A forwarder whose own periodic check happened to land inside that window found an incomplete set, treated it as a failed download, and then waited six hours before trying again — even though the files were ready moments later. Because every activation has such a window, any forwarder could hit it.
Worse, there was no way out of it from the app. The six-hour wait was keyed to the version being offered and deliberately ignored a fresh request, so pressing Upgrade now did nothing on a host with Auto-upgrade switched on — which is the recommended setting. Clearing it meant turning Auto-upgrade off, requesting the upgrade, and turning it back on, or waiting out the six hours. A fresh upgrade request now clears the wait, so Upgrade now does what it says.
Everything the forwarder reports read normally throughout: it stayed connected, its configuration showed as applied, and it kept delivering logs. Only the update was stuck.
0.68 — October 26, 2026
Section titled “0.68 — October 26, 2026”-
A forwarder stopped at an awkward moment no longer leaves a stray copy of itself behind. When a forwarder is stopped, a safeguard added in 0.66 makes sure the part that does the collecting stops with it, rather than being left running and holding the network port it listens on. That safeguard checked whether the collecting process was still the one it was watching — and if that check could not be carried out at that instant, on a busy or memory-pressured host, it treated the process as already gone and quietly switched itself off for the rest of that forwarder’s life. Being unable to look is not the same as having looked and found nothing, and the two are now told apart: a check that cannot be completed is retried instead of ending the watch. A host where the necessary information is not available at all says so in the forwarder’s log instead of appearing to be protected.
Left unaddressed, the stray copy keeps delivering logs, so every health indicator reads normally while it holds the port the real forwarder needs — and the next update is silently blocked until someone restarts the service by hand. On one of our own hosts that went unnoticed for eleven hours.
0.67 — October 15, 2026
Section titled “0.67 — October 15, 2026”- A healthy update is no longer rolled back for doing its own setup. The protection that reverts an update whose new version will not run was counting every start of the forwarder rather than every crash, and a forwarder is started for reasons that are not crashes — a probe before it runs, the start itself, and a stop-and-start each time it is handed new settings. A perfectly healthy update whose first minute happened to include a couple of settings changes could use up the whole allowance and be reverted as though it had crashed repeatedly. A start that the service manager or the supervisor ended deliberately no longer counts against the update; one that ended because the forwarder itself stopped still does, so a genuinely broken update is still caught.
- An update that was rolled back now reports the version it is running. When the protection above does revert an update, the forwarder asks for a restart so the version shown in the app matches what is on its disk. Before, a reverted forwarder could carry on reporting the newer version it was no longer running.
- Each part of an update is checked after it is put in place, not before. A part that did not land is reported rather than assumed, so a half-applied update is visible instead of looking like a success.
- Nothing changes about what a forwarder collects, and there is nothing to re-configure. A forwarder with Auto-upgrade on takes this on its own; Windows forwarders are updated by reinstalling with the newer bundle.
0.66 — October 7, 2026
Section titled “0.66 — October 7, 2026”- The installers now accept an install directory:
--install-diron Linux and macOS,-InstallDiron Windows. Everything the forwarder keeps — its program, its settings and access token, and its queue of undelivered logs — goes under the folder you choose. Without the option nothing changes. An existing install is never moved; to relocate one, uninstall it and install again with a fresh credential. - Fixes a case where restarting or stopping the forwarder service could leave the previous copy running in the background. That copy kept holding the forwarder’s local port, so the restarted forwarder could not start even though the service still looked active. A forwarder whose launcher is force-stopped by its service manager now cleans up after itself as well.
- A forwarder that updates itself now receives every part of the update, not only the program: the files that carry the restart fixes above are delivered alongside it and are checked against the published release before they are used. A forwarder takes those parts once the collector it reports to is also up to date; until then it keeps updating its program as before and leaves the rest in place, so an older collector delays the restart fixes rather than leaving a forwarder half-updated.
0.65 — September 23, 2026
Section titled “0.65 — September 23, 2026”- Fixes the version shown after a self-upgrade: the forwarder now reports the version of the binary it’s actually running, instead of the version it started up with.
- Delivers rotated forwarder credentials automatically.
- Adds per-process GPU memory to NVIDIA GPU metrics.
0.64 — September 22, 2026
Section titled “0.64 — September 22, 2026”- The forwarder now honors the tenant-wide upgrade window and version hold configured under Configure → Log Forwarders → Settings. A forwarder only self-upgrades inside the window you allow, and stops at the version you pin.
0.63 — September 15, 2026
Section titled “0.63 — September 15, 2026”- Fixes a case where the periodic update check could skip a release that only changed a supporting component rather than the forwarder program itself.
- On macOS, a forwarder running in tail mode now reports its new version correctly after a self-upgrade. Previously, the restart it needed required privileges that mode doesn’t have, so the reported version stayed stale.
0.62 — September 14, 2026
Section titled “0.62 — September 14, 2026”The release that completed self-upgrade end to end on Linux and macOS: a forwarder can now update itself — the forwarder program, its launcher, and its control binary — with no manual reinstall, and it automatically rolls back if a new build fails to come up. macOS builds are signed and notarized.
Versions between 0.48 and 0.62 were internal build-and-test steps taken while self-upgrade was being proven out, and were never published as installable releases. That’s why the published sequence below jumps from 0.48 to 0.62.
0.48 — September 4, 2026
Section titled “0.48 — September 4, 2026”- Adds NVIDIA GPU telemetry to the Linux forwarder.
docs built 2026-11-12 · 945a2dec2