Skip to main content Skip to navigation Skip to footer

Monitoring & Diagnostics

Watch and follow along as we check machine health, inspect containers, review services, and run diagnostics.

Tutorial: Monitoring & Diagnostics

This tutorial demonstrates the monitoring and diagnostic commands available in rdc: health checks, container inspection, service status, vault overview, and environment diagnostics.

Prerequisites

Interactive Recording

What You’ll See

The recording above walks through each step below. Use the playback bar to navigate between commands.

Step 1: Run diagnostics

rdc doctor

Checks your local environment: Node.js, CLI version, renet binary, configuration, and virtualization support. Each check reports OK, Warning, or Error.

Step 2: Machine health check

rdc machine health server-1

Fetches a comprehensive health report including system uptime, disk usage, datastore usage, container counts, storage SMART status, and any identified issues.

Step 3: View running containers

rdc machine containers server-1

Lists all running containers across all repositories on the machine, showing name, status, state, health, CPU usage, memory usage, and which repository owns each container.

Step 4: Check systemd services

rdc machine services server-1

Lists Rediacc-related systemd services (Docker daemons, loopback aliases) with their state, sub-state, restart count, and memory usage.

Step 5: Vault status overview

rdc machine vault-status server-1

Provides a high-level overview of the machine: hostname, uptime, memory, disk, datastore, and total repository counts.

Step 6: Scan host keys

rdc config scan-keys server-1

Refreshes the SSH host key stored in your config for the machine. Useful after a machine rebuild or IP change.

Step 7: Verify connectivity

rdc term server-1 -c "hostname"
rdc term server-1 -c "uptime"

Quick SSH connectivity check by running inline commands on the remote machine.

Next Steps