Quick start

What you end up with

Six containers running on one Linux host, with a console you can sign in to from a browser. It is enough to evaluate the product, connect a few hosts and run read-only inspections, and it can serve as the starting point for a small production environment.

You do not have to prepare a database password, JWT secret, administrator password, cloud access keys or AI keys. The installer generates what it needs locally; everything else is optional and configured after you sign in.

Four steps

Do them in order; each has a guide that spells out the commands. After the first two you already have a console you can sign in to.

1. Settle three things: which machine to install on, whether it can reach the public internet, and which address the managed hosts will use to reach it. The third is the one people get wrong most often — get it wrong and Agents cannot connect. See Before you install.
2. Download and install: pick the online or offline package, verify it, extract it, run one command, then sign in and change the one-time password. See Download and install.
3. Connect your first host: create a registration token in the console and install the Agent on the target machine. Assets, jobs and inspections all need at least one host. See Connect your first Agent.
4. Set up maintenance: what to back up, how to prove a backup can actually be restored, and what to check around an upgrade. See Backup, recovery and upgrades.

About the License

The licenses/trust-bundle.json inside the package is just a set of signature-verification public keys. Everyone receives the same file, the platform will not start without it, and it always ships with the package, so it needs no attention from you.

A signed License bound to your organization is a separate file you request from us. Without it the platform still installs and the console still opens, but onboarding hosts, running jobs and similar features report that they are not licensed. You do not need one to look around; you do need one to actually manage hosts.

• To request one, write to weiwendi@aiops.red and describe your operating system, CPU architecture and the number of nodes you plan to manage.
• Import it on the console License page once you have it. No reinstallation and no container restart are required.

Check these before you go further

Only when all of these hold is the environment actually usable, rather than merely having started its containers.

1. Sign in again with your new password and confirm the mandatory password-change prompt is gone.
2. Connect one test host and confirm the hostname, IP address and system details in the asset inventory match reality.
3. Confirm in Agent management that the host is online rather than stuck at never-connected.
4. Run one fixed read-only inspection and check its timing and results. Job execution is on by default, so an approved job really does run commands on its target host.