Scans & findings

A scan is the core of Parsivex. It reads your resource inventory and the CloudWatch metrics attached to it, runs each detector over that data, and produces findings: a specific resource, why it looks wasteful, and what it is costing you per month. Detectors cover compute, storage, databases, caching, networking, and logging, and each one has its own thresholds rather than a single blunt rule.

These articles explain what happens during a scan and how long it takes, what every finding type means in plain English, and how severity and monthly savings figures are calculated — including why those figures are estimates based on observed usage and list pricing, not a promise. Read them before you act on a number, so you know what it does and does not account for.

Findings have a life beyond the report. You can dismiss the ones that are intentional, snooze the ones you plan to deal with later, and let the next successful scan resolve the ones you actually fixed. That is where realized savings comes from: Parsivex credits a fix only when the resource stops showing up in a scan that completed cleanly, so a failed or partial scan never quietly marks your work as done. The rest of this section covers the findings inbox, partial scan warnings, reports and share links, and the cost assistant that answers questions about what a scan found.