Quickstart
From an empty Linux server to 3AM watching your incidents in shadow mode, in under 30 minutes.
This path installs 3AM on one Linux server from the install bundle and connects your monitoring and one approval channel. 3AM starts in shadow mode: it diagnoses and proposes, and changes nothing.
Other platforms
On Kubernetes, follow Kubernetes. On Windows Server, start with Windows Server. The console steps from step 4 onwards are the same everywhere.
Prepare the server
A Linux server with 4 cores, 8 GB of memory and 50 GB of disk, and Podman or Docker installed:
sudo dnf install -y podman
podman --versionCopy the bundle and install
tar -xf 3am-0.1.0.tar && cd 3am-0.1.0
./install.shThe installer checks the server, verifies the bundle's checksums and signature, loads the images, starts 3AM and runs a preflight check. At the end it prints the console address and the admin token. Keep the token; it is shown once. It is also stored in the data volume.
Open the console
On the server, open http://127.0.0.1:8700. From your laptop, use an SSH tunnel:
ssh -L 8700:127.0.0.1:8700 you@the-serverSign in with your name and the admin token.
Install the licence
The setup wizard shows this install's fingerprint. Send it to 3AM and you receive a licence file for this install. Upload it on the same screen. See Licensing.
Connect monitoring and approvals
The wizard walks you through each tool and tests every connection before saving it:
- Monitoring: for example Prometheus and Alertmanager
- Approvals: for example Slack or PagerDuty
- Optionally your systems (Kubernetes, databases) and code
Set the policy and discover
Keep Shadow selected, check the approval escalation order, then run Discover. 3AM maps your services, alert rules, repositories and owners, and turns on the checks that match your technologies.
What happens next
From now on every new alert opens an incident in the console. Each one shows the confirmed root cause, the evidence, and what 3AM would have done. After a week, the digest shows how often 3AM agreed with your team. When a service has a good record, raise it to L1 (two people approve that change), and 3AM starts fixing it with one approval per action.