Skip to main content

Adding a host

The first host​

A fresh workspace opens on an onboarding dashboard: it shows your team key (issued automatically) and the install command for each platform, with a copy button. Run the command on your server; the page polls and redraws itself the moment the first heartbeat arrives.

Every next host​

Click Add host in the Hosts module. The dialog shows the same one-line install command with your active team key filled in:

  • Linux and macOS: one curl | bash line.
  • Windows: one PowerShell line (run as Administrator).
  • Docker and Kubernetes: container and DaemonSet variants.

The host appears in the grid within about a minute. Nothing else is required: discovery and the service catalog activate on their own. What the command does on the host, and what to check if it does not appear, is covered on the agent side: Installation and Troubleshooting (wakora doctor on the host is the fastest answer).

The team key is a bootstrap credential for your whole fleet. Issue and revoke keys in Settings, Agent keys; see Team and access.

Two guards worth knowing at scale: registration respects your plan's host quota (a host past the cap is refused at install; reinstalling an existing host always works), and registrations per key are rate limited against runaway scripts. A large rollout (hundreds of hosts via Ansible) needs no babysitting either way: a rate-limited host parks its key and registers itself minutes later on its own.

Naming and labels​

A host reports its hostname as the display label. Rename it from the host page (the name is only a label; identity is stable regardless).

Pinning the agent version​

The host page has a lifecycle card showing the agent version. Pin locks the host to an exact release: the agent converges to it, upward or downward, and stays there until you unpin. Useful for change-frozen environments; the rest of the fleet keeps auto-updating.

Removing a host​

On the host page, Remove asks you to type the hostname to confirm, then:

  • revokes the host's key and purges its stored telemetry,
  • tells the live agent to uninstall itself (the order is cryptographically signed and only valid for that host),
  • resolves the host's open incidents and takes it out of every list.

A host that was offline during removal is locked out on its next reconnect. The same removal can be done from the host itself with wakora uninstall, see Uninstalling.