Română
Português
EspañolAdding servers to the monitoring
Fleet is where your servers live: on your premises, in a data centre, or in any cloud. Each runs a small sensor; the portal shows which report, which have gone quiet and which need an update.
Add a server
- Step 1
Open Fleet and choose Add servers
In the portal go to Security & Compliance › Fleet and choose Add servers. You need to be an owner or administrator.
- Step 2
Copy the command
The portal creates an enrolment link valid for 24 hours and shows the command that uses it. One link enrols as many servers as you like until it expires.
- Step 3
Run it on the server, as root
Paste the command into a terminal on each server. It installs the sensor, registers the server under its hostname in your organisation, and starts it.
- Step 4
Watch it arrive
The Add servers panel lists each server as it registers, then as it sends its first report, usually within a minute or two.
curl -fsSL https://totuldigital.com/portal/security/fleet/install/<your-token> | sudo bash
What the server needs
- A current, supported 64-bit Linux distribution, on x86-64 or ARM64.
- Root access for the install.
- Outbound TCP 1514 to sensors.totuldigital.com for the sensor, and HTTPS (443) to totuldigital.com during the install. Nothing inbound.
- About 100 MB of disk and a few tens of MB of memory. The sensor reads logs and runs checks; it does not inspect traffic.
For Windows servers and other systems, write to support@totuldigital.com and we will enrol them with you.
Check a sensor on the server
systemctl status totuldigital-sensor journalctl -u totuldigital-sensor -n 50
If the service runs but Fleet shows the server as silent, the usual cause is a firewall blocking outbound 1514. Test it from the server:
nc -vz sensors.totuldigital.com 1514
What the states mean
| State | Meaning | What to do |
|---|---|---|
| Online | The sensor checked in recently. | Nothing. |
| Offline (silent) | No check-in for a while. Its events stop counting as evidence until it returns. | Open the server: the portal lists what to check (service, firewall, clock, disk). |
| Waiting | Registered, but no first report yet. | Wait a few minutes; if it stays, check the service and port 1514. |
| Out of date | The sensor is older than the monitoring service. | Choose Update on the server, or select several and update them together. |
Manage the fleet
Open a server for its details: operating system and kernel, hardware, hardening score, vulnerabilities, installed packages, listening ports and its recent events. Owners and administrators can restart or update the sensor, or remove the server from monitoring. Remove stops the monitoring; uninstall the package on the server as well.
Labels such as Production, Office or Cloud group servers on the Fleet screen and on Topology. The list can be filtered, searched and exported as CSV.
Related
Still stuck?
Write to us with what you tried and what you saw. A person answers, in writing, on business days.