Collector Login

Most collector administration happens in the portal, on Platform → Administration → Collectors. The console is for the few things the portal cannot do: setting the appliance's own network configuration before it can reach the platform, registering it, and fetching files from it.

Reaching the Console

Log in at the VM's console, or over SSH on port 22, with the operating-system account set up when the appliance was built — the root password chosen during the Rocky Linux installation, or the cloud provider's own account for an image launched in AWS, Azure or GCP. Without root, prefix each command below with sudo.

Management Commands

The mgmt command reconfigures the appliance's network interface, eth0, to match your network:

mgmt network set dhcp
mgmt network set static <ip_address> <gateway> <netmask>
mgmt dns set <dns1> <dns2>

Use info in place of set to view the current settings — mgmt network info, mgmt dns info.

It also registers the collector with your Fluency instance, using the token from the portal:

mgmt add_server https://<your-instance-hostname> <your-token>

See Connecting the Collector to a Fluency Cloud Instance for where the token and the host name come from. Running it again replaces the previous registration. The installer can register a new collector as it installs, with its --server and --token options; mgmt add_server is how to change the registration after that.

Files You May Need

File	What it is
/etc/certs/ca.crt	The certificate authority the collector generated for itself at install time, which signs the certificate its TLS syslog listeners present. Devices sending to the collector over TLS have to trust this file — the CA downloaded from the platform's Syslog Ports page does not validate a collector. See TLS Trust.

After Connecting

Once the collector is registered and its status dot is green, configuration moves back to the portal: its syslog listeners, network view and health are on Managing Collectors.