DC Overview Documentation

Complete GPU Datacenter Monitoring Suite

View the Project on GitHub cryptolabsza/dc-overview

DC Watchdog + Fleet Management: Config Checklist

Use this to verify your quickstart config (e.g. /root/test-config.yaml) when DC Watchdog is enabled.

Intended flow

  1. Deploy – Quickstart runs; Fleet Management and dc-overview start. Go agents can be installed if an API key is available (e.g. from .secrets.yaml).
  2. First-time in Fleet – DC Watchdog is not shown as enabled until the user clicks Link Account and completes SSO. This is intentional so the user explicitly enables and validates the key.
  3. After SSO – Fleet stores the validated API key. That key can be refreshed; Go agents register with the Watchdog server and receive worker tokens for identification and encrypted comms.

Config checklist (e.g. /root/test-config.yaml)

Example minimal snippet

components:
  dc_overview: true
  ipmi_monitor: true   # or false
  dc_watchdog: true

ssh:
  username: root
  auth_method: key
  port: 100
  key_path: ~/.ssh/ubuntu_key

watchdog:
  server_url: https://watchdog.cryptolabs.co.za
  install_agent: true
  agent_use_mtr: true

servers:
  - name: master
    server_ip: 41.193.204.66
    has_gpu: true

Secrets (e.g. .secrets.yaml): set ipmi_ai_license or watchdog_api_key so quickstart can install agents; Fleet will still require “Link Account” + SSO the first time.