Monitor the fleet
Track collector instances, their health, and whether they're running the right config.
Open a fleet to see its dashboard — a live view of every collector instance that has connected, refreshed automatically every 15 seconds. A stats strip at the top summarizes the fleet; the instance grid lists each collector with its status, the config version it's running, and when it was last seen.
Instance status
Telflo derives each instance's status from what it has been served, what it has been assigned, and what the collector reports back:
| Status | Meaning |
|---|---|
| In sync | The collector applied the configuration it was assigned. |
| Pending pickup | A new config has been assigned but the collector hasn't received it yet. |
| Applying | The collector received the config and is applying it (or hasn't reported a result yet). |
| Apply failed | The collector rejected the config — it needs attention. |
| Stale | No heartbeat recently — the collector has gone quiet. |
A colored dot accompanies each status (green for in sync, amber for pending/applying, red for apply failed, grey for stale).
Online vs. stale
Instances report in on a heartbeat:
- Online — seen within the last 5 minutes.
- Stale — no contact for more than 15 minutes.
The dashboard also color-codes the Last seen column so you can spot a collector that has just gone quiet (within the warn/danger thresholds) before it tips fully stale.
Apply failed needs you. A failed apply stays visible even if the collector then goes quiet — Telflo keeps surfacing the failure so it isn't masked by a missing heartbeat. Inspect the config and the collector logs, fix the issue, and roll out a corrected version.
Refreshing
The grid polls every 15 seconds on its own. You can also trigger a manual refresh of the instances list; the button shows a spinner while it fetches.
Managing instances
From the fleet detail page you can also:
- Rename an instance to something recognizable.
- Migrate instances to another fleet.
- Delete an instance that's been decommissioned.
Next
- Roll out a new configuration version — Update the config.
- Understand instances that lag behind — Configuration drift.