# The action log

Find out who did what on your infrastructure, and how it turned out.

## The steps

1. Open **Action log**, under **Actions**.
2. Filter with **All**, **Actions**, **Deployments** or **Consoles**.
3. Read a row: **When**, **Action**, **Machine**, **Source**, **Requested by**, **Outcome**, **Effect**.
4. Expand the detail of an outcome to read the hypervisor's raw report: it is often the only place where the real cause is written.

## What to know

- **It is open to all users of the company.** Knowing what was done does not require the right to do it.
- **The Effect column** gives a state transition for an action, a duration and a data volume for a console.
- **The author survives the deletion of their account**: an audit trail that becomes anonymous when someone leaves is no longer one.
- **A row is created before the action.** Even an action that fails, or never leaves, leaves its trace.

## Three places, three questions

| You are looking for | Go to |
|---|---|
| Who acted on the infrastructure **from Naoshift** | **Action log** |
| What **changed between two collections**, whatever its origin | **Events** |
| Who signed in, what changed in **Naoshift's settings** | **Settings › Security & deliverables › Audit trail**, for administrators |

> A detected change says "something moved". An action says "this person did this at this second". For an outage, look at both.

### The log is empty

Nobody has acted from Naoshift yet. What is done directly on the hypervisor does not appear there: it shows up in **Events**, at the next collection.

### I do not see Audit trail

It is reserved for company administrators. The action log stays open to all.
