Monitoring

Rediacc provides built-in monitoring commands to inspect machine health, running containers, services, repository status, and system diagnostics.

Machine Health

Get a comprehensive health report for a machine:

rdc machine health server-1

This reports:

• System: uptime, disk usage, datastore usage
• Containers: running, healthy, unhealthy counts
• Storage: SMART health status
• Issues: identified problems

Use --output json for machine-readable output.

List Containers

View all running containers across all repositories on a machine:

rdc machine containers server-1

Column	Description
Name	Container name
Status	Uptime or exit reason
State	Running, exited, etc.
Health	Healthy, unhealthy, none
CPU	CPU usage percentage
Memory	Memory usage / limit
Repository	Which repository owns the container

Options:

• --health-check — Perform active health checks on containers
• --output json — Machine-readable JSON output

JSON output includes full container details (labels, port_mappings, image, id) plus repository (resolved name), repository_guid (original GUID), domain, and autoRoute.

List Services

View systemd services related to Rediacc on a machine:

rdc machine services server-1

Column	Description
Name	Service name
State	Active, inactive, failed
Sub-state	Running, dead, etc.
Restarts	Restart count
Memory	Service memory usage
Repository	Associated repository

Options:

• --stability-check — Flag unstable services (failed, >3 restarts, auto-restart)
• --output json — Machine-readable JSON output

JSON output includes full service details with repository (resolved name) and repository_guid (original GUID).

List Repositories

View repositories on a machine with detailed stats:

rdc machine repos server-1

Column	Description
Name	Repository name
Size	Disk image size
Mount	Mounted or unmounted
Docker	Docker daemon running or stopped
Containers	Container count
Disk Usage	Actual disk usage within the repository
Modified	Last modification time

Options:

• --search <text> — Filter by name or mount path
• --output json — Machine-readable JSON output

JSON output includes name (resolved) and guid (original GUID), and nests each repository’s containers (with domain, autoRoute, repository/repository_guid) and services arrays.

Vault Status

Get a complete overview of a machine including deployment information:

rdc machine vault-status server-1

This provides:

• Hostname and uptime
• Memory, disk, and datastore usage
• Total repositories, mounted count, Docker running count
• Detailed per-repository information

Use --output json for machine-readable output.

Test Connection

Cloud adapter only. In local mode, use rdc term server-1 -c "hostname" to verify connectivity.

Verify SSH connectivity to a machine:

rdc machine test-connection --ip 203.0.113.50 --user deploy

Reports:

• Connection status (success/failed)
• Authentication method used
• SSH key configuration
• Public key deployment status
• Known hosts entry

Options:

• --port <number> — SSH port (default: 22)
• --save -m server-1 — Save verified host key to machine config

Diagnostics (doctor)

Run a comprehensive diagnostic check of your Rediacc environment:

rdc doctor

Category	Checks
Environment	Node.js version, CLI version, SEA mode, Go installation, Docker availability
Renet	Binary location, version, CRIU, rsync, SEA embedded assets
Configuration	Active config, adapter, machines, SSH key
Virtualization	Checks if your system can run local virtual machines (rdc ops)

Each check reports OK, Warning, or Error. Use this as a first step when troubleshooting any issue.

Exit codes: 0 = all passed, 1 = warnings, 2 = errors.