Scanners
Monitors the health and connectivity status of all registered scanners. Shows each scanner's current status, version, network identity, and last heartbeat time. Scanners with no heartbeat for 2+ minutes are marked offline. To provision or configure scanners, go to Config > Scanners.
Fields & Columns
| Name | Description |
|---|---|
| Name | The unique identifier assigned to this scanner during provisioning |
| Status | Current state: Active (heartbeat within 2 min), Pending (awaiting first connection), Offline (no heartbeat 2+ min), Disabled (manually disabled) |
| Version | Scanner binary version reported during heartbeat |
| External IP | Public IP address the scanner connects from, as seen by the ingest node |
| Internal IP | Private/LAN IP address reported by the scanner itself |
| Hostname | System hostname of the machine running the scanner |
| Last Seen | Relative time since the last heartbeat (e.g., "30s ago", "5m ago") |
| Last Error | Most recent heartbeat rejection reason (invalid key, IP binding violation, disabled). Clears on successful heartbeat. |
How To
Troubleshoot an Offline Scanner
- Click the scanner row to open the detail panel
- Check the error banner (red) for the last rejection reason
- Review the event timeline for the sequence of events leading to the outage
- Common causes: API key invalidated (regenerate-token was called), container restarted without API key persistence, IP binding violation from a new NAT address
Gotchas
- This page is read-only health monitoring. To provision, edit, or delete scanners, use Config > Scanners.
- A scanner showing "Pending" has been provisioned but has never connected — verify the scanner binary is running and can reach the ingest endpoint.
- If a scanner shows "Invalid API key", the API key was invalidated (e.g., by regenerating the provisioning token). The scanner must re-register with a new token.
- Heartbeat errors are cleared when the scanner successfully heartbeats again — a past error does not mean the scanner is currently failing.
API Calls (2)
| Method | Path | Description |
|---|---|---|
| GET | /api/scanners | List all registered scanners with status and metadata |
| GET | /api/scanners/:id/events | Scanner event timeline (state changes, heartbeat errors) |
Related Pages
- Overview — Architecture diagram showing scanner nodes
- Ingest — Ingest nodes receive scanner heartbeats and results
- DNS — Scanner DNS card shows PTR and ASN data for registered scanners
- Config > Scanners — Provisioning and configuration of scanners
- Scanner Heartbeat — Heartbeat protocol details including metrics and IP binding enforcement