Discovery Pipeline
The Pipeline view is the run history for discovery — every pass over your accounts and regions, with what triggered it and how it ended.
Run record
| Field | Meaning |
|---|---|
| Run | The scan run identifier |
| Trigger | What started it — schedule, onboarding, or a manual request |
| Status | How it ended |
| Started / Completed | When it ran, and how long it took |
Why the run history is a first-class view
An inventory without provenance is a claim. When someone asks whether a resource is really gone, the answer depends entirely on whether the last run over that account actually finished — and a failed or partial run leaves an inventory that looks complete and is not. Putting run status on its own page means a stale picture is visible as a stale picture.
Scan scope follows entitlement
What the pipeline runs depends on which products the organisation has:
- Estate only — discovery runs on its own.
- Estate and Onam Security — the full pipeline runs, and both products read the same output.
There is nothing to configure for this. Scheduling is automatic and follows the entitlement.