Monitoring Your Forwarders
Configure → Log Forwarders lists every forwarder you’ve installed, with its status, group, and recent activity.
Reading the status
Section titled “Reading the status”Each forwarder shows a status dot:
| Status | Meaning |
|---|---|
| Pending approval (greyed out) | A new forwarder has connected but hasn’t been approved yet. Approve it to enable delivery over an encrypted connection. |
| Online / healthy (green) | Reporting in and running normally. |
| Not seen yet / stale (amber) | Approved, but hasn’t checked in recently. Common right after install, or if the host has been offline. |
| Offline / unhealthy (red) | Was reporting, but has stopped. |
Confirming delivery
Section titled “Confirming delivery”Open a forwarder’s row for its detail drawer:
- Logs (past hour) and a sparkline of recent volume — the clearest signal that data is actually flowing.
- Config — whether its current configuration (from its assigned Group’s Profiles) has been applied.
- Last seen and its reported version.
The drawer also lists checks for the forwarder. One of them, Collector data delivery, looks at the collector this forwarder reports through: everything a forwarder sends leaves your network by way of that collector, so a collector that is connected for management but isn’t getting data through leaves its forwarders looking healthy and empty. When that check fails it names the collector and the address and port it needs to reach. It reads Unknown when GridNMS can’t tell yet (for example, the collector enrolled moments ago), and a warning, not a failure, when the collector itself is offline.
For a definitive check, go to Log Search and filter to the host — you should see recent entries.
When a forwarder has delivered nothing
Section titled “When a forwarder has delivered nothing”Log delivery is the first check in the drawer. When nothing has arrived in the last hour it tells you which of these you are looking at, because they need different responses:
| What the check says | What it means | What to do |
|---|---|---|
| No logs arrived, and the forwarder is collecting from a named source, with an information icon and no warning colour | The forwarder is enabled, connected and healthy, and the sources it was given have simply not produced anything. This is normal for a source that is only written to when something happens, such as a job scheduler’s completion log on a host that has not run a job. | Nothing, unless you expect logs. If you do, confirm the files or journal exist on the host and that the forwarder can read them. |
| None are expected: no log source is enabled (amber) | The forwarder has nothing to collect. | Turn on a source in the Forwarder Profile applied to its group. See Forwarder Management. |
| Something is likely stopping them from being delivered (red), followed by the checks to look at | A source is enabled, and a check on the connection is failing: the forwarder’s credential, its management connection, the collector’s listener, or the collector’s own delivery. | Open the checks it names and fix those. |
| Whether this forwarder can deliver cannot be confirmed right now (amber) | A source is enabled and nothing is known to be wrong, but a link cannot be checked yet, for example the forwarder has never reported in or a new configuration has not been confirmed. | Wait for the next check-in, or see the first steps below. |
GridNMS looks at the last hour of delivery and cannot see inside the host, so it cannot tell you whether a quiet forwarder has ever delivered, or whether a source it is waiting on exists. The explanation is shown with a neutral colour on purpose: a healthy forwarder with nothing to send is not a fault.
The host’s own metrics
Section titled “The host’s own metrics”A forwarder’s Metrics tab charts the machine it runs on, over the last hour, 6 hours, or 24 hours:
- System — CPU, memory, and disk read/write. No module turns these on; every forwarder reports them once it is linked to a device. If this tab is empty on a healthy forwarder, that link is the thing to check first — see Linking a forwarder to a device.
- GPUs — a card per NVIDIA GPU in the host, with utilization, memory, temperature, and power draw. This one is a module you turn on for the host’s profile, and it is Linux only — see Turning on GPU metrics.
Seat usage
Section titled “Seat usage”Log Forwarders share a plan-wide seat allowance. Configure → Log Forwarders shows how many you’re using against your plan’s limit. If you’re at your limit, approve fewer forwarders or upgrade your plan — see Pricing.
A forwarder keeps its seat for as long as it exists. Removing or replacing the collector it connected through does not free the seat, and the forwarder stays in credential rotation. A forwarder tied to a monitored device does not use a seat. To free one, delete the forwarder.
First steps when a forwarder goes quiet
Section titled “First steps when a forwarder goes quiet”- Confirm the process is running on the host:
- Linux:
sudo gridnms-forwarder statusorsudo systemctl status gridnms-forwarder - macOS:
sudo gridnms-forwarder status - Windows:
gridnms-forwarder statusorGet-Service GridNMSForwarder
- Linux:
- Check the agent’s own log for errors — the exact path is in Installing a Log Forwarder for each platform.
- Check what it is set up to collect. A forwarder that is connected and healthy but sending nothing is usually a module that is off, or on with nothing to read. Open the host’s Configuration tab and read the resolved module list — see Checking what a forwarder actually runs.
- Check network reachability from the host to the collector it’s configured to use — the forwarder only makes outbound connections, so a firewall or routing change on either end can cut it off.
- Check the collector itself — if every forwarder pointed at one collector goes quiet together, the problem is the collector, not the forwarders. See Monitoring & Managing Collectors.
- Once connectivity returns, a forwarder reconnects on its own — nothing to re-approve, and anything queued while it was disconnected delivers automatically.
Related pages
Section titled “Related pages”- Forwarder Management — Groups, Profiles, and what each forwarder collects.
- Monitoring & Managing Collectors — the collector side of the same connection.
- Logs & Log Search — confirm what’s actually arriving.
docs built 2026-11-12 · 945a2dec2