Files and repositories
This page lists where a Nexus Telemetry Fleet collector keeps its files on each platform, and where the packages and images come from. Each path is created by the package at install, or by the collector at its first run.
Collector
| What | Debian, Ubuntu, RHEL and Fedora | macOS | Windows | Docker |
|---|---|---|---|---|
| Binary | /usr/bin/nf-collector |
/usr/local/bin/nf-collector, with nf-collector-uninstall beside it |
C:\Program Files\NexusFleet\nf-collector.exe |
/usr/local/bin/nf-collector |
| Config | /etc/nexus-fleet/collector.toml, mode 0640 |
/Library/Application Support/NexusFleet/collector.toml |
C:\ProgramData\NexusFleet\collector.toml |
none, environment only |
| Data directory | /var/lib/nexus-fleet |
/Library/Application Support/NexusFleet |
C:\ProgramData\NexusFleet |
/var/lib/nexus-fleet, the nf-data volume |
| Local store | <data>/collector.db |
<data>/collector.db |
<data>\collector.db |
<data>/collector.db |
| Log | <data>/logs/collector.log, kept to 5 files of 10 MB |
<data>/logs/collector.log, kept to 5 files of 10 MB. The system also writes the collector’s console output to /Library/Logs/NexusFleet/collector.log |
<data>\logs\collector.log, kept to 5 files of 10 MB |
<data>/logs/collector.log, kept to 5 files of 10 MB |
| Service | nf-collector, and nf-collector-updater.path with its .service, which run the updates the dashboard triggers |
com.nexustelemetry.nf-collector, a launch daemon defined in /Library/LaunchDaemons |
NexusFleetCollector |
none. The container is restarted by Docker, with --restart always |
| Reading the log | journalctl -u nf-collector -f |
tail -f /Library/Logs/NexusFleet/collector.log |
open the log file, or the Logs panel on the setup page | docker logs nf-collector |
These paths are inside every data directory, whatever the platform.
| File | What it is |
|---|---|
certs/collector.crt |
the device certificate |
certs/collector.key |
its private key, a PEM file at mode 0600 |
certs/ca.crt |
the CA certificate that signed it |
certs/transport-root.crt |
the root certificate the collector checks the fleet server against when it connects |
device.id |
the collector’s identity. A collector that still has this file attaches to its existing record when it enrols again |
enrolled.json |
the enrolment record: the collector id, the fleet server address and the interval |
status.json |
the status file the running collector writes, which nf-collector status reads |
Run by hand, the collector uses ./data in the working directory unless
NF_DATA_DIR names another.
Note: the Linux packages create /var/log/nexus-fleet and give the service
write access to it, and nothing writes there. The log is
<data>/logs/collector.log.
Repositories, channels and images
| Fact | Value |
|---|---|
| Download host | https://fleet-downloads.nexustelemetry.com |
| Repository signing key, served from the marketing site | https://nexustelemetry.com/nexustelemetry-public.asc |
| Image signing key, for cosign | https://nexustelemetry.com/cosign.pub |
| Local keyring path | /usr/share/keyrings/nexustelemetry.gpg |
| apt source file | /etc/apt/sources.list.d/nexustelemetry-fleet.list |
| apt source line | deb [signed-by=/usr/share/keyrings/nexustelemetry.gpg] https://fleet-downloads.nexustelemetry.com/apt stable main |
| rpm repository file | /etc/yum.repos.d/nexustelemetry-fleet.repo |
| rpm base URL | https://fleet-downloads.nexustelemetry.com/rpm/stable/, with gpgcheck and repo_gpgcheck both on |
| Channels | alpha, beta, stable |
| Registry | registry.nexustelemetry.com |
| Collector image | registry.nexustelemetry.com/nf-collector, amd64 and arm64, anonymous pull, cosign-signed |
| Image tags | :<version>, fixed to that release. :alpha, :beta and :latest point at the newest release on the alpha, beta and stable channels |
| macOS package | NexusFleetCollector-<version>.pkg |
| Windows installer | NexusFleetCollector-<version>.msi |
| deb | <package>_<version>-1_<arch>.deb. In the version, a pre-release hyphen such as 0.0.1-alpha.25 is written as a tilde, 0.0.1~alpha.25 |
| rpm | <package>-<version>-<release>.<arch>.rpm, with the same tilde |
A release is built and signed once. Promotion publishes the same files to the next channel and moves the image tag to the same image. Nothing is rebuilt.
Release paths
| Path | Contains |
|---|---|
https://fleet-downloads.nexustelemetry.com/fleet/<channel>/<version>/ |
Every file of that release, with SHA256SUMS and its signature. Never changed once written |
https://fleet-downloads.nexustelemetry.com/fleet/<channel>/latest.json |
The manifest: the current version, and each file’s address and SHA-256. Rewritten on every publish and promotion |
https://fleet-downloads.nexustelemetry.com/apt/dists/<channel>/, https://fleet-downloads.nexustelemetry.com/apt/pool/ |
The apt repository |
https://fleet-downloads.nexustelemetry.com/rpm/<channel>/packages/, .../repodata/ |
The rpm repository |
There is no latest directory. https://fleet-downloads.nexustelemetry.com/fleet/<channel>/current/
holds the macOS package and the Windows installer without a version in the
name, each beside a .sha256 file with its checksum and version, so a
download link never changes. The fleet server’s update check and the
collector’s update both read the manifest.
See Release channels for which channel a collector follows and how to change it, and Private deployment for the fleet server.