Setup wizard
Licence, tools, policy and discovery, without editing a file.
A new install opens the wizard at /setup and stays there until you select Finish setup. You can come back any
time from Settings → Open guided setup.
Licence
Copy the install fingerprint, request a licence, then upload licence.json (or paste it).
Monitoring
Where alerts come from and where 3AM reads metrics: Prometheus/Alertmanager, Splunk, Datadog, Grafana, PagerDuty. Choose a tile, fill in the form, select Test connection. The test shows what 3AM found (for Prometheus: jobs, services, alert rules, targets) before you Save.
Approvals
Where people approve what 3AM proposes: Slack, Symphony, PagerDuty, Twilio voice, e-mail. Add more than one to build an escalation chain.
Systems
What 3AM may check and, with approval, change: Kubernetes, databases (MySQL, PostgreSQL, Oracle, SQL Server), SSH hosts, HTTP automation (Ansible Tower, Jenkins…).
Code and tickets
Optional: repositories to search (GitHub, GitLab, Bitbucket, any Git server), tickets (Jira, ServiceNow) and your CMDB (ServiceNow) for service ownership.
Policy
How 3AM starts. Shadow is recommended: 3AM proposes and records, and changes nothing. Order the approval channels (the first is asked at once; the others after the delay you set) and set the most actions per service per hour.
Discover
3AM reads what you connected (CMDB, monitoring labels, repositories, clusters), links services to their alerts, repositories, owners and dependencies, and turns on the check packs for the technologies it found. When it finishes, select Finish setup.
How secrets are handled
Fields marked with a lock are secrets. 3AM stores them in files only it can read and never shows them again. When editing a connector, leave a secret field blank to keep the stored value. Connection tests may use the values you typed, but they are only saved when you select Save.