> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valar.space/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage reporting

> Review created events and saved bookings for AOI overflights and ground-station passes.

Open **Reporting → Usage** in **Operations**. Select the last 7, 30, 90 or 365
UTC dates and optionally select spacecraft. Without a spacecraft filter, the
report includes historical activity from archived spacecraft.

## Event activity

The Events section shows separate totals and daily charts for:

| Metric             | What counts                               |
| ------------------ | ----------------------------------------- |
| AOI events created | Published AOI overflight forecast records |
| AOI events booked  | Saved AOI overflight bookings             |
| GS passes created  | Published ground-station pass candidates  |
| GS passes booked   | Saved ground-station pass bookings        |

Created events use their creation/publication date. Bookings use the date you
saved them. Neither uses the scheduled date of the overflight or contact.
A booking does not establish that an observation or contact was executed.

AOI and ground-station reporting follow the same rules. Refreshing forecasts or
deleting their source records does not subtract historical usage. Newly published
replacement forecasts add creation activity, so these counts are not counts of
unique physical encounters. Repeated requests for an existing booking and its
archive copy do not add another booking.

## Reading historical coverage

Each metric states whether its history covers the selected period. **Partial
history** means the displayed total is a subtotal starting at the shown UTC time;
earlier activity is unavailable. A partly tracked first day is marked **partial**
in the chart. Dates before tracking began are not plotted as zero.

**No activity** means tracking was available but recorded nothing for your
selection. **History unavailable** means the report cannot establish activity
for that period. A failed request shows a separate error and **Retry** action.