Guide

What would make 3AM more useful next, what it can see of your estate (coverage, service by service), what each page is for, and the tips.

Guide (/guide, g g, in the Help menu) tells owners and admins what would make 3AM more useful, and what each part of the console is for. Everything is worked out from what the server already says; a recommendation disappears by itself once done.

What 3AM can see

Six kinds of evidence, each measured by depth (how many of your services it reaches), not by a tick per kind:

KindFromWithout it
Alerts and metricsPrometheus, VictoriaMetrics, Datadog, Splunk, Grafana, Alloy, PagerDutyNothing opens an incident
People to askSlack, Symphony, e-mail, PagerDuty, Twilio, xMatters3AM can diagnose, never act
DatabasesSQL connectionsA database cause stays a suspicion
Where it runsKubernetes, Argo CD, serversNo rollback, no host evidence
Code and runbooksRepositoriesNo change behind a failure, no runbook excerpts
Tickets and changesServiceNow, JiraNo change records, no ticket trail

"4 of 12 services", which are still dark, and what to do about them. Shown on every connection step of setup, on Connections, and here.

Recommendations

In order: a failing connection; missing evidence; evidence that reaches only some services; services the licence covers that 3AM doesn't watch yet; a second approval channel; a first service at L1; judging closed incidents; single sign-on; a second owner; teams; an investigator model; a first Study, or a new one. One that doesn't apply can be set aside, and brought back here. The top three show on the Overview.

Tips

One short tip at the top of some pages (Incidents, Estate, Autonomy, Audit log, Learned, Digest, Keychain) until closed. Show the tips again is here.

On this page