# Overview

> The console's home page. What 3AM is judged by (ended by 3AM, time given back, actions verified, hand-overs, causes proven), what needs you, and 3AM's own health.

Source: https://docs.3am.si/console/overview · Markdown: https://docs.3am.si/console/overview.md · All docs: https://docs.3am.si/llms.txt
3AM is an on-prem AI on-call engineer for regulated enterprises (https://3am.si).

The overview (`/`, `g o`) answers one question first: **is 3AM doing its job?** Then what needs you.

## The status line

One row: 3AM's light, and a small button when something waits for you (an approval, a connection with a problem, a
halt).

## What 3AM is judged by

From the server's scorecard over the last 30 days (`GET /v1/episodes?scorecard=1`):

| Figure                       | Meaning                                                                                                                                |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Ended by 3AM**             | Resolved and restored, of the incidents that needed someone; how many at night or on a weekend; alert to ended against your own figure |
| **Time given back**          | Engineer time 3AM replaced, only from your own figures (Settings → Your numbers), never claimed without them                           |
| **Actions verified**         | Fixes 3AM ran whose verification passed, and any it took back                                                                          |
| **Handed over, triage done** | When people had to act: the median time to the triage, and the share within 90 seconds                                                 |
| **Root cause proven**        | Incidents whose cause a check proved                                                                                                   |

Below: failures (and those 3AM ended) per day, what became of them by result, what needs you, where it happens, how
sure 3AM was, the latest incidents, and 3AM's own health.

## Results

Every incident ends as one of:

| Result        | Meaning                                                                             |
| ------------- | ----------------------------------------------------------------------------------- |
| `resolved`    | The cause was proven and fixed, and the fix verified                                |
| `restored`    | Service is back by a verified move; the cause is still open, and the record says so |
| `handed_over` | With people, with the triage                                                        |
| `linked`      | Part of another incident                                                            |
| `cleared`     | Stopped by itself                                                                   |
| `shadow`      | Recorded; nothing done                                                              |

## Make 3AM sharper

For owners and admins: the top three recommendations from the [Guide](https://docs.3am.si/console/guide) (a failing connection, missing
evidence, a second approval channel, a first service at L1, …). Nothing is shown when there's nothing to recommend.

## Counting

The overview counts **distinct failures**. Linked symptoms are counted apart, so one database failure seen from three
services is one failure. With nothing in 30 days it shows one panel (*No failures*, or *Nothing is being watched
yet*), never cards of zeros. Colour is rationed: the accent means "3AM did this".