Monitor a fleet
Track a fleet's collectors, their status, and the configuration they run.
This page describes how to monitor a server fleet from its detail page. The Collectors tab lists every collector that has connected. The list refreshes automatically every 15 seconds while the page is visible, and you can refresh it manually. A stats strip at the top summarizes the fleet: collectors, how many are online, version drift, and when the token expires.
This page covers server fleets. Kubernetes bridge fleets report through a bridge and use a different status model. See Kubernetes fleets.
The collector table
| Column | Contents |
|---|---|
| Name | The collector's name. Select it to open a read-only details dialog with the remaining fields: instance ID, token sync state, configuration name, target version, collector version, and the last reported error. |
| IP Address | The machine's self-reported primary private IPv4 address. It stays unique per machine even when several hosts share one egress address. |
| Deploy Group | The deploy group the collector belongs to. |
| Variable Group | The variable group whose values the collector resolves. Shows org defaults when none applies. See Vault. |
| Status | The collector's configuration status. See the table below. |
| Effective Version | The configuration version the collector is running, linked to that version in the editor. |
| Last seen | When the collector last reported, as a relative time with a liveness dot: green within 1 minute, amber within 2 minutes, red beyond that. |
| Actions | Edit collector, to rename the collector or pin it to a configuration, and delete. |
Find collectors
The collector list is paginated, 50 collectors per page, with Prev and Next controls and a Showing count in the footer. Collectors appear newest first; select the Last seen header to sort by last contact instead.
To find specific collectors, type in the search box above the list and press Enter. The search matches a fragment of the collector's name, IP address, deploy group name, or the name of the configuration it targets, ignoring case. The search, page, sort order, and active tab are kept in the page URL, so a filtered view can be bookmarked and shared.
Collector status
Telflo derives each collector's status from the version it has been served, the version it has been assigned, and what the collector reports. The assigned version is the version the collector is pinned to, if any, otherwise its deploy group's assigned version.
| Status | Meaning |
|---|---|
| In sync | The collector applied the configuration it was assigned. |
| Pending pickup | A new version is assigned, but the collector has not received it yet. |
| Applying | The collector received the version and is applying it, or has not reported a result yet. |
| Apply failed | The collector rejected the configuration. It needs attention. |
| Stale | No recent heartbeat. The collector has gone quiet. |
A colored dot accompanies each status: green for in sync, amber for pending pickup and applying, red for apply failed, and gray for stale.
Online and stale
Collectors report on a heartbeat.
- Online: confirmed within the last 2 minutes.
- Stale: no contact for more than 15 minutes. A collector that already reported In sync or Apply failed keeps that status; Stale applies to collectors that have not yet confirmed their assigned version.
An apply failure stays visible even if the collector then goes quiet, so the failure is not masked by a missing heartbeat. Inspect the configuration and the collector logs, fix the issue, and roll out a corrected version.
Manage collectors
From the Actions column you can:
- Rename a collector, or pin it to a published configuration and version, with Edit collector. The pin can target any published configuration, not only versions of the group's configuration; the option marked group default clears a pin. See Update the configuration.
- Delete a decommissioned collector.
The details dialog opened from a collector's name also has an Edit collector button.
Group-wide configuration changes are made on the Deploy Groups tab. The detail page also has a Tokens tab for the fleet's tokens and install links. See Tokens & security.
Next steps
- Roll out a new configuration version. See Update the configuration.
- Understand collectors that lag behind. See Configuration drift.
Last updated on