Readyset Docs

Audit every target in your fleet concurrently. Get a per-target report plus fleet-wide insights.

rdst fleet audit runs the same analysis as rdst audit against every target in your fleet, concurrently. On top of the per-target reports, it generates fleet-wide insights: cross-instance Readyset candidates, estimated cost savings, and fleet-level health.

Common usage

# Audit every target in the fleet
rdst fleet audit

# Audit one group (e.g. an Aurora cluster)
rdst fleet audit --group orders-prod

# Filter by tag
rdst fleet audit --tag aurora --tag writer

# Capture live workloads (per target)
rdst fleet audit --duration 5m

# Save a named fleet snapshot
rdst fleet audit --save march-baseline

# Compare against an earlier snapshot
rdst fleet audit --diff march-baseline

What you get back

The audit produces two things:

One per-target audit report (same format as rdst audit --target X, emailed separately per target by default)
A fleet-level summary with cross-instance analysis

Example fleet summary

Fleet Audit Summary — 2026-04-21
────────────────────────────────────────────────────────────────
  Fleet:                12 targets audited (group: orders-prod)
  Capture window:       5 minutes
  Duration:             4m 12s concurrent

  Health:
    Right-sized:        8
    Oversized:          3   (could be downsized, $2,840/mo savings)
    Under-provisioned:  1   ⚠  prod-orders-writer hitting 94% CPU

  Readyset opportunity (fleet-wide):
    High (80+):         5 targets
    Medium (50-79):     4 targets
    Low (<50):          3 targets

  Top cross-instance recommendations:
    1. 7 of 12 instances run similar `SELECT * FROM orders WHERE ...` query.
       Deploy a Readyset cache once at the cluster level instead of 7 times.
       Estimated combined savings: 31s/min saved across the fleet.

    2. Missing index on customers(segment, created_at) recurs in 9 targets.
       Propagate the same fix to the whole cluster.

  Per-target actions:
    ✓ prod-orders-writer      → rdst audit show audit_prod-orders-writer_...
    ✓ prod-orders-reader-1    → rdst audit show audit_prod-orders-reader-1_...
    ✓ prod-orders-reader-2    → rdst audit show audit_prod-orders-reader-2_...
    ...

Full reports emailed to ellen@example.com.
Fleet snapshot saved: fleet_snapshot_orders-prod_20260421_120402

How concurrency works

rdst fleet audit audits targets in parallel, typically with a small per-target concurrency limit to avoid hammering your network or exhausting LLM rate limits. RDST manages the pool for you — you do not need to tune it manually.

Large fleets take time. A 50-target fleet audit with --duration 5m typically takes 6–8 minutes wall clock, not 250 minutes.

If you're worried about timing, start with rdst fleet audit --group <small-group> to audit a handful of targets first, then expand. You can always audit subsets.

Filtering the fleet

Every fleet command supports the same filters:

# By group (typically a cluster or environment)
rdst fleet audit --group orders-prod

# By tag (repeatable — multiple tags AND together)
rdst fleet audit --tag aurora --tag writer

# By group AND tag
rdst fleet audit --group orders-prod --tag reader

If you aren't sure what groups and tags exist, rdst fleet list shows them all.

Fleet-wide insights vs per-target

The fleet summary answers questions you can't answer one database at a time:

"Which of my 50 databases would most benefit from Readyset?" — The summary ranks Readyset opportunity fleet-wide, so you cache the top few instead of hunting manually.
"Is this index missing everywhere, or just here?" — Cross-instance recommendations surface patterns that repeat across many databases, so you fix them at the cluster level.
"Are we over-provisioning?" — Sizing verdicts across the fleet, with estimated monthly dollar savings from downsizing oversized instances.
"Did anything regress this month?" — --diff <baseline> highlights every target where metrics, top queries, or cache opportunity scores changed significantly.

The email flow

Like rdst audit, the default output is email. The first fleet audit prompts for email verification, then sends:

One email per target with the per-target HTML report
One email with the fleet summary and links to all per-target reports

Use --verbose to print everything to the terminal instead. --json produces a single machine-readable fleet report.

Flags reference

Flag	What it does
`--group <name>`	Only audit targets in this group
`--tag <tag>`	Only audit targets with this tag (repeatable)
`--duration <spec>`	Per-target live capture window (e.g. `2m`, `5m`)
`--save <name>`	Save the fleet snapshot under a friendly name
`--no-save`	Don't persist the snapshot
`--diff <baseline>`	Compare against a saved fleet snapshot
`--no-insights`	Skip LLM analysis (faster; per-target metrics only)
`--json`	JSON output
`-y, --yes`	Auto-accept any cache-deploy prompts

A complete workflow

Going from zero to a fleet audit on day one:

# 1. Discover
rdst fleet discover --regions us-east-1

# 2. Verify connectivity
rdst fleet status

# 3. Audit with a 5-minute capture
rdst fleet audit --duration 5m --save baseline-2026-q2

# 4. Act on the top cross-instance recommendation
rdst analyze --hash <from-report> --target <top-candidate>
rdst cache deploy --target <top-candidate> --mode docker
rdst cache add <hash> --target <top-candidate>-cache

# 5. Three months later, measure progress
rdst fleet audit --duration 5m --diff baseline-2026-q2

rdst fleet audit