Upgrade
Upgrade 3AM with the same command you installed it with. Your data and settings are kept, and the previous version comes back if the new one doesn't start.
When a new version is out, the console's Settings page says so, with the command to run.
Run the install command again, on the server:
curl -fsSL https://get.3am.si/install | shOn a server whose models run on its own GPU, add -s -- --profile gpu, so the download includes the model runtime.
The installer shows the settings it's reusing from last time, and asks before going ahead. To change one, stop (Ctrl-C) and run it again with that option.
What's kept
Everything: the audit log (its chain carries on across versions), incidents, connections, settings, secrets, the licence, your sealed packs, and the admin token.
On a server, the installer's own settings are in ~/.3am/install.env, and copies of your key files in ~/.3am/keys/.
Old 3am-<version> folders can be deleted.
If the new version doesn't start
The installer prints its log and starts the previous version again, with its data and settings. Nothing is lost. Send us the log and we'll help.
During the upgrade
3AM is unavailable briefly while its container is replaced.
- Investigations in progress are recorded as stopped. An alert that's still firing opens a new incident.
- A fix waiting for approval is closed, because its investigation stopped. Requests to change autonomy carry on, with the approvals already given.
- What changed detection takes about ten minutes to settle on any tool whose readings changed shape.
Taking a backup first is always a good idea.
Common questions
Yes: curl -fsSL https://get.3am.si/install | sh -s -- --version 0.4.41. On Kubernetes, helm upgrade … --version 0.4.41.
Install it the same way, with --version. Take a backup first: an older version may not read everything a newer one
wrote.
A key file it remembered has gone, or its settings file couldn't be read. The install carries on without it; set that option again in the console's Settings, or pass it to the installer.