Software
New releases of the Collector and the Log Forwarder are published as they become available. Software is where your organization decides which release its agents run, and when a new one is taken. Your agents install the release that is activated here, so a new release only reaches them once it has been activated for your organization.
Open it from Configure → Service Management → Software.
What you’re looking at
Section titled “What you’re looking at”Software is a table with one row for each package type on each operating system, for example Collector on macOS, Collector on Linux, and Log Forwarder on macOS, Linux and Windows. Each row has seven columns:
| Column | What it shows |
|---|---|
| Package Type | Collector or Log Forwarder. |
| Operating System | macOS, Linux or Windows. |
| Activated Version | The release your agents on that operating system are following, with a Roll back button beside it. |
| Activation Datetime | When that release became the activated one. |
| Current Release | The newest release that has been published for that operating system, with an Activate button beside it. |
| Current Release Datetime | When that release was published. |
| Automatic Activation | How soon a newly published release is activated for you. |
Times are shown in your organization’s timezone, which you set under Configure → System Configuration → Global Settings → Timezone.
A dash (—) means there is no value: nothing has been activated yet, or no release has been published.
If no release has reached your instance at all, there is no table yet and the page says No software to manage. That is the expected state on a brand-new deployment, and on an instance with no outbound connection to GridNMS — releases are published by GridNMS and reach your instance from there, so an instance that can’t fetch them has nothing to activate. Your agents keep running the release they were installed with.
A release is published for both processor types of an operating system together. If the two ever differ, the row shows the older version and the earlier time.
On a self-hosted deployment there is also an Other self-upgrading components card. It is a placeholder: there are no additional self-upgrading components on a self-hosted deployment today, so it has nothing to manage.
Choosing when new releases are activated
Section titled “Choosing when new releases are activated”Automatic Activation is set for each row, so you can take a release on Linux straight away while keeping macOS where it is. It has five choices:
| Choice | What happens |
|---|---|
| Manual only | Your organization does not take new releases automatically. A new release stays available until you activate it. |
| Immediately | A new release is activated as soon as it is published. |
| After 1 day | A new release is activated one day after it is published. |
| After 3 days | A new release is activated three days after it is published. |
| After 5 days | A new release is activated five days after it is published. |
Manual only is where every row starts. A delay gives you time before a new release reaches your organization. When a row is waiting on a delay, hover over its Automatic Activation choice to see when the release will be activated.
If you change a row’s choice, the release it has already moved to stays activated. For example, switching from Immediately to Manual only does not move your agents back to an older release.
Activating a release
Section titled “Activating a release”Select Activate beside a row’s current release to activate it for that operating system. The button is unavailable when the current release is already the activated one or nothing has been published.
Activating takes effect for your whole organization on that operating system. Whether an individual agent then installs the release depends on that agent’s own automatic-upgrade setting and release group, or on you asking it to upgrade now.
If the release you are activating is older than the one currently activated — for example when a release has been withdrawn — GridNMS asks you to confirm before moving your organization back.
Rolling back
Section titled “Rolling back”Roll back returns that operating system to the release that was activated before the current one. You are asked to confirm first. Only the single previous release is kept, so the button is unavailable until there is one to return to. Rolling back one row does not change any other row, and a release you have rolled back from is not activated again automatically; you can activate it later.
Occasionally a roll back cannot cover every machine type on that operating system. This happens when the earlier release was never saved for one of them — usually because it was published for the other machine type first. GridNMS tells you which ones when it happens, and those machines stay on what they are running now and are not offered an update until a newer release is activated. Every other machine type returns to the earlier release as usual.
Who can change it
Section titled “Who can change it”This page sits behind administrator access, like the rest of Service Management — without it the section doesn’t appear in Configure at all. Changing Automatic Activation, activating and rolling back need administrator write access on top of that; with read-only access the controls are disabled and say why.
Where to go next
Section titled “Where to go next”- Service Management — health of the background services behind GridNMS.
- Collector Release Notes and Log Forwarder Release Notes — what changed in each release.
docs built 2026-11-12 · 945a2dec2