Browse and search documentation
Onboard your first Agent
Enroll a specific host using the platform’s installation instructions, checking architecture, version, registration token and first heartbeat.
On this page
Before installation
- Obtain authorization to maintain the target host, identify its OS and CPU architecture and confirm that your delivered version supports the combination.
- Confirm the host can reach the designated Agent gateway and that you have permission to install the service. Do not use the platform server’s loopback address as a remote Agent destination.
- Use the package and instructions supplied by the platform. Do not copy another environment’s registered Agent directory with its identity and certificate state.
Single-host onboarding
- In Agent management’s installation guide, select the platform, architecture and an available matching release.
- Create or select the registration token for this installation. Check expiry, allowed uses and any exact-host binding. Do not reuse a default single-use token across hosts.
- Download the package and run the environment-generated installation command on the intended host. Gateway, token and TLS materials are environment-specific and must not be copied from someone else’s example.
- Return to the Agent list and verify hostname, OS, architecture, version and recent heartbeat, including online status.
- Check the corresponding asset and project binding, then run an authorized read-only check.
Interpret onboarding results
| Observation | Check first |
|---|---|
| No node appears | Installation completion, token validity and gateway reachability |
| Record exists but is offline | Agent service, last heartbeat, certificates and network |
| Platform or architecture mismatch | Select the correct package rather than forcing another architecture’s binary |
| Duplicate or incorrect identity | Check for copied registered state; stop expanding enrollment and ask an administrator |
Expand beyond one host
Validate networking, permissions and version on one host, then group further hosts by OS, architecture and maintenance window. Track online and failed hosts with reasons. Cloud-assistant installation and batch onboarding depend on provider and delivery version; do not assume one path covers every cloud, datacenter or Windows domain.
Something differs from your environment?
Send your deployment version, page and a redacted description so we can investigate and update the guide.
weiwendi@aiops.red