Impact and the lookback
The business report in your own money (what 3AM returned, where it came from, how the figures are made), saved as PDF, and the lookback over your last 90 days of incidents.
Impact (/impact, g b) is the business report, for owners and admins.
The report
- One figure at the top: what 3AM returned, in your organisation's money; the return on what 3AM costs.
- Four counts, and where the value came from, line by line with each sum shown.
- What happened: failures and fixes over the period, how fast, what became of them, what was left untaken in shadow, where.
- How the figures are made.
Periods: 30 days, 90 days, 12 months. Save as PDF is the browser's print-to-PDF of A4 sheets drawn in the page: text stays text and nothing leaves the install. Each sheet carries your logo and 3AM's. Also CSV.
Your numbers
3AM ships with no rates and assumes none. Counts and times are measured; money is those counts times your own rates, and always marked an estimate. Until the currency and the four needed figures are answered, the report shows no money and the overview shows investigations as a count instead of hours.
| Figure | Field | Needed |
|---|---|---|
| Currency | currency | Yes |
| An engineer's hour | engineer_hour | Yes |
| Page to cause, minutes | triage_min | Yes |
| Fix, minutes | fix_min | Yes |
| Time to restore by hand, minutes | manual_resolve_min | Yes |
| An hour of disruption | downtime_hour | No (not counted) |
| A call-out | callout | No |
| What 3AM costs a year | annual_cost | No |
Asked in setup, on Impact and in Settings → Your numbers; kept in config/impact.json, admin only
(GET/PUT /v1/impact). They stay on the install: not in the usage statement, never sent anywhere.
Before 3AM: your own record (the lookback)
One button reads the last 90 days (7 to 365) of resolved incidents from ServiceNow or PagerDuty: how many, how long they stayed open, how your team ended them where the record says, and which of those moves 3AM makes on this install with approval. It states what happened and what 3AM is able to do; it never says 3AM would have fixed them. Only the counts are stored. Notes the usual words don't settle are read by System 1 when configured.
curl -s -X POST -H "Authorization: Bearer $T" -d '{"days":90}' $URL/v1/lookback # 409 when nothing keeps historyDigest
What 3AM did, or in shadow would have done, next to what your team did; agreement, readiness for L1, and how to tell 3AM what your team did.
Estate
Your services, owners, teams, dependencies, alerts, workloads, databases and repositories, where each link came from, what isn't placed yet, and how discovery never drops anything.