CLI

Inspecting a store that will not open

The inspect command group reads a store's diagnostic artifacts straight from disk without starting the engine - because the stores most worth inspecting are the ones that will not start.

# Reads the store's diagnostic artifacts from disk, without starting the engine.
NetlyDB.Cli inspect --store ./data collections
NetlyDB.Cli inspect --store ./data wal Orders
NetlyDB.Cli inspect --store ./data wal verify Orders
NetlyDB.Cli inspect --store ./data snapshot Orders
NetlyDB.Cli inspect --store ./data recovery
NetlyDB.Cli inspect --store ./data audit verify --json

It is inspection only. There are no repair commands: a repair needs exclusive control of the store and must leave an audit record, and a tool pointed at a directory can establish neither.

• WAL inspection is structural: it checks framing, checksums, sequence and stream identity, not document contents. A clean verdict means the bytes are sound.
• audit verify reports on the chain it finds and names the declared actions this build does not record, so an empty trail is not mistaken for an assurance.

Talking to a running node

The same tool can call a running node's REST API with --url - listing collections, running queries and explains, exporting and importing, and reading replication status and health.