Check lakehouse table health with Lakehouse Guard

At a glance

Learning objectives

• Read a table-health report before planning maintenance
• Generate a compaction plan instead of running compaction ad hoc
• Understand when the guard blocks maintenance actions

What you need

• A Delta or Iceberg table due for maintenance
• Warehouse credentials with read access
• [object Object]

Steps

1. Run /table-health for a table-health read. (from plugin-lakehouse-guard )
2. Run /plan-compaction for the compaction plan. (from plugin-lakehouse-guard )
3. Run /expire-snapshots for the snapshot-expiry plan. (from plugin-lakehouse-guard )
4. Know what the plugin is — a Delta/Iceberg table maintenance advisor plus a guard that blocks compaction or snapshot expiry during peak ingestion windows. (from plugin-lakehouse-guard )
5. Expect the two capabilities, table-maintenance and guardrails, on every interaction. (from plugin-lakehouse-guard )

Check yourself

• A /plan-compaction issued during the ingestion window is blocked by the guard instead of executing.
• The three commands run in order — health read, compaction plan, expiry plan — each producing a plan, not an execution.

Worked example

amp plugin add de-agent/lakehouse-guard

/table-health
/plan-compaction
/expire-snapshots

capabilities: [table-maintenance, guardrails]
permissions: { filesystem: read, network: warehouse, credentials: warehouse }
skills: [skill-iceberg-maintenance, skill-delta-optimizer]

Sourced from

• Lakehouse Guard

Security scan

Last sweep 2026-10-24: 0 finding(s), 0 marked as examples.

Common gotchas

• The guard blocks compaction or snapshot expiry during peak ingestion windows — plan around them.
• Commands produce plans; executing them still needs your warehouse credentials and judgement.
• Permissions are filesystem read with warehouse network and credentials — the plugin reads, it does not hold broad access.

Production considerations

• Keep maintenance inside the plugin's guardrails rather than bypassing them during incidents.
• Plan compaction against the ingestion calendar so peak windows are known before planning.

Diagram

lakehouse guard
   |
   |- /table-health --> current health read
   |
   |- /plan-compaction --> maintenance plan
   |
   |- /expire-snapshots --> expiry plan
   |
    |- peak ingestion window? --> guard blocks execution

Registry stats