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

# Reports

> Read the compliance Overview page, export results, and validate a live fleet against an external build sheet.

The Luumen UI gives you two ways to consume compliance results: the live **Acceptance to Run → Overview** page, and downloadable **Reports** for sharing or compliance documentation.

## Overview page

Open **Acceptance to Run → Overview** to see live results across your fleet:

* **Needs attention** — a list of hosts with recent failed or unchecked runs, each with a sparkline of the last 12 checks.
* **Overall performance** — a donut showing pass vs fail counts across whatever scope you've selected (default: all groups).
* **Host group details** — every group with its in-compliance ratio, expandable into hosts and into individual checks.

Use the **View by** toggle at the top of the group details panel to flip between a host-group view and a flat host view. The flat view is useful when you're triaging a specific incident and don't care about group rollups.

### Filtering and drill-down

Click any group to expand its hosts. Click a host to expand its checks. Click a specific check to see the rule, the expected vs actual values, and recent history.

Use the **All Status** dropdown to narrow to a specific result type (Pass, Fail, Error, Not checked) when you only want to see what's broken.

## Reports

The **Reports** section in the sidebar gives you a snapshot view of compliance status across all managed hosts and groups, plus the option to export.

### What's in a report

| Field               | Description                                                                       |
| ------------------- | --------------------------------------------------------------------------------- |
| Total hosts checked | Count of hosts included in the most recent agent run.                             |
| Passes              | Count of checks that evaluated true.                                              |
| Failures            | Count of checks that evaluated false.                                             |
| Errors              | Count of checks that could not be evaluated (missing property, host unreachable). |
| Connection errors   | Count of hosts the agent could not reach.                                         |

### Export to CSV or PDF

From the Reports page, click **Export** to download a snapshot in either CSV (for further analysis) or PDF (for compliance documentation). The export reflects whatever filters and time range you've applied to the current view.

### Saved views

You can apply filters (group, check, time range) and save the resulting view for quick access. Saved views are useful when you have a regular reporting cadence — for example, a "Production weekly" view that filters to production groups for the past 7 days.

## Validate against a build sheet

If your team already maintains a build sheet — a spreadsheet of what each host is supposed to look like — Luumen can validate the live fleet against that spreadsheet:

<Steps>
  <Step title="Upload the build sheet">
    From **Reports**, upload your build sheet (CSV format).
  </Step>

  <Step title="Run a comparison">
    Luumen compares each row in the build sheet against the matching live host based on hostname or identifier, and reports rows that don't match.
  </Step>

  <Step title="Review discrepancies">
    The output lists each mismatched property, the expected value (from the sheet) and the actual value (from the agent). Use this to either fix the live host or update the build sheet.
  </Step>
</Steps>

This is the most direct way to use Luumen for migration validation: build sheet describes what was supposed to be provisioned, agent reports what actually got provisioned, comparison surfaces the gap.

## Reading the donut

The overall performance donut weights every check equally — one failure on a niche check counts the same as one failure on a critical one. If your team weights checks differently in practice, lean on the **Needs attention** list and on group-level rollups instead of the global percentage. The percentage is useful as a trend (is it going up or down over time?) more than as an absolute score.

## How fresh are reports?

Reports show the state of the most recent agent run that includes each host. If you're seeing data that looks stale, check the timestamp at the top of the Overview page — it's the time of the last completed run for the current scope.