Fleet and Audit
Audit a single database, or an entire fleet. Discover RDS instances. Capture live workloads. Diff audits across time.
RDST has two complementary features for managing and auditing many databases:
- Audit — a deep health report for a single database target. Metrics, sizing verdict, Readyset cache opportunity score, top queries, live workload capture, and LLM insights in one command.
- Fleet — bulk management of multiple targets. Import from a CSV, discover from AWS, check connectivity across all of them, and run audits concurrently.
The two are designed to be used together: rdst fleet discover fills your target
list, then rdst fleet audit runs rdst audit against every target in parallel.
What is a fleet?
A fleet is the set of database targets RDST knows about, scoped to the machine it is installed on. There is no shared fleet across users or machines — everyone manages their own list.
Fleets automatically exclude Readyset cache targets (those created by
rdst cache deploy). Fleet commands act on upstream databases only.
Targets in a fleet can be organized with:
| Dimension | Example | Set by |
|---|---|---|
| Group | orders-prod, staging | --group on import/discover, or rdst fleet configure |
| Tag | aurora, writer, pii-sensitive | --tag on import/discover |
You can filter most fleet commands by group or tag:
rdst fleet list --group orders-prod
rdst fleet status --group orders-prod
rdst fleet audit --group orders-prod --duration 5m
rdst fleet audit --tag aurora --tag writerAurora clusters discovered with rdst fleet discover are automatically grouped by
cluster name and tagged aurora plus writer or reader per instance endpoint.
Single vs fleet audit
rdst audit and rdst fleet audit produce the same per-target report. The
differences are:
rdst audit | rdst fleet audit | |
|---|---|---|
| Targets | One (--target) | Many (every fleet member, or filtered by --group / --tag) |
| Execution | Sequential | Concurrent |
| Snapshot | Single-target snapshot | Fleet snapshot grouping every target's report |
| Extra insights | None | Fleet-wide summary (cross-instance Readyset candidates, estimated savings) |
| Output | Emailed report (default) or --verbose terminal | Same, plus a fleet summary |
Start with rdst audit --target <name> to learn the workflow against one database,
then graduate to rdst fleet audit once you have a fleet configured.
The audit report
Every audit report contains:
| Section | What it tells you |
|---|---|
| Metrics | Database version, size, connection count, cache hit rate, read/write ratio |
| Sizing verdict | oversized, right-sized, or under-provisioned (driven by pricing + utilization) |
| Cache opportunity score | 0–100 rating for Readyset candidacy, based on query mix and cacheability |
| Top queries | Ranked by total time and call frequency, each with EXPLAIN context |
Live capture (with --duration) | Queries RDST saw actually running during the window |
| LLM insights | Health assessment, bottleneck analysis, index recommendations, Readyset candidates, prioritized next steps |
The audit report is emailed by default. The first rdst audit on a new
machine prompts you to verify an email address. Every subsequent audit sends
there automatically with a link to a hosted HTML version. Use --verbose to
print the report to the terminal instead.
Sections in this guide
rdst audit
Deep single-target audit with --duration, --diff, exports, and email flow.
Setting up a fleet
Import from CSV, discover from AWS, configure groups and credentials.
rdst fleet audit
Audit every target in a fleet concurrently. Filter by group or tag.
Snapshots and diff
Revisit past audits, compare across time, and track changes to your fleet.