Setup wizard

The steps a new install walks you through, from sign-in and the licence to connecting your tools and discovering your estate. No files to edit.

A new install opens on the setup wizard and stays there until 3AM is up and running. You can come back to it any time from Settings → Open guided setup. Owners and admins can run it, and invite colleagues from the Team page along the way.

Before the wizard, you create the first owner by signing in with the admin token the installer printed (Sign-in).

Sign-in

How your people will sign in: your identity provider, your directory, or emailed codes. You can change it later (Single sign-on).

Licence

The wizard asks whether this is your organisation's first install.

  • First install: redeem a trial code, or upload your licence (Get a licence).
  • We run 3AM elsewhere already: set this site up from your Keychain. Connections, sign-in, policy and people arrive from the home.

Your figures

A few questions about what incidents cost you: how many a month, how long they take to fix, what an engineer's hour costs. 3AM uses only your own figures to show what incidents cost a year. Skip it if you like; no money is shown until it's answered (Impact).

Monitoring

Where alerts come from: Prometheus and Alertmanager, VictoriaMetrics, Grafana, Datadog or Splunk. Test connection shows what 3AM found before you save. You need at least one.

Approvals

Where people approve fixes: Slack, Symphony, PagerDuty, xMatters, a phone call through Twilio, or email. Add more than one to escalate from one to the next. You need at least one.

Systems

What 3AM may check and, with approval, fix: Kubernetes, Argo CD, databases (MySQL, PostgreSQL, Oracle, SQL Server), servers over SSH, and HTTP automation. Optional, but without them 3AM can diagnose and not fix.

Code and tickets

Optional: your repositories (GitHub, GitLab, Bitbucket or any Git server), tickets (Jira, ServiceNow), and your CMDB for service owners.

Policy

Every service starts in shadow: 3AM proves and proposes, and changes nothing. Here you order the approval channels and set how long to wait before moving to the next, and the most fixes per service per hour.

Keychain

On Enterprise and Strategic, make this install the home, so your other sites take its setup by themselves. Or carry on without.

Discover

3AM reads everything you connected at once, links services to their alerts, repositories, owners and dependencies, and turns on the packs for the technologies it finds. Anything it can't place waits on the Estate page. Then 3AM is watching.

On every connection step, What 3AM can see shows how much of your estate each kind of evidence reaches so far.

Secrets (the fields with a lock) are saved to files only 3AM can read, and never shown again. When editing a connection, leave a secret blank to keep it.

On this page