sample-output.json

{
  "tool": "monad-preflight",
  "overall": "FAIL",
  "interrupted": false,
  "counts": {
    "fail": 1,
    "pass": 4,
    "skip": 1,
    "warn": 2
  },
  "results": [
    {
      "name": "virtualization",
      "title": "Bare metal (no hypervisor or container)",
      "verdict": "PASS",
      "summary": "no hypervisor or container detected",
      "elapsed_ms": 0
    },
    {
      "name": "cpu-spec",
      "title": "CPU meets core count and base clock minimums",
      "verdict": "PASS",
      "summary": "16 cores, base_clock 4.5GHz",
      "metrics": [
        {
          "name": "physical_cores",
          "value": 16,
          "unit": "count",
          "threshold": 16
        },
        {
          "name": "base_clock",
          "value": 4.5,
          "unit": "GHz",
          "threshold": 4.5
        }
      ],
      "elapsed_ms": 0
    },
    {
      "name": "ram",
      "title": "System RAM meets minimum",
      "verdict": "PASS",
      "summary": "31.3 GiB RAM",
      "metrics": [
        {
          "name": "total",
          "value": 31.3,
          "unit": "GiB",
          "threshold": 32
        }
      ],
      "elapsed_ms": 0
    },
    {
      "name": "kernel-version",
      "title": "Kernel version supported and free of known bugs",
      "verdict": "PASS",
      "summary": "kernel 6.8.0-79-generic meets the minimum and is not on the known-bad list",
      "elapsed_ms": 0
    },
    {
      "name": "smt",
      "title": "SMT / HyperThreading disabled",
      "verdict": "WARN",
      "summary": "SMT/HyperThreading is enabled; Monad docs require disabling it in BIOS",
      "advice": "Disable SMT (AMD) / HyperThreading (Intel) in BIOS before running a validator.",
      "elapsed_ms": 0
    },
    {
      "name": "cpu-governor",
      "title": "CPU frequency governor set to performance",
      "verdict": "WARN",
      "summary": "32 of 32 CPUs are not on 'performance' (schedutil on 32); downclocking adds wake latency",
      "advice": "Set the governor to 'performance' on all cores: cpupower frequency-set -g performance (persist via your init/service manager).",
      "elapsed_ms": 0
    },
    {
      "name": "triedb-device",
      "title": "TrieDB drive: 2TB+ NVMe with 512-byte LBA",
      "verdict": "SKIP",
      "summary": "no TrieDB device identified (no --triedb-dev and no /dev/triedb symlink yet)",
      "advice": "Pass --triedb-dev /dev/nvmeXnY[pZ] to check the drive you intend to dedicate to TrieDB.",
      "elapsed_ms": 0
    },
    {
      "name": "nvme-latency",
      "title": "Storage write tail latency (O_DIRECT random 4KiB)",
      "verdict": "FAIL",
      "summary": "storage tail latency too high (p99 2635.0us, p99.9 5898.0us, O_DIRECT random write); per-command latency this erratic will stall TrieDB",
      "metrics": [
        {
          "name": "p50",
          "value": 120,
          "unit": "us"
        },
        {
          "name": "p99",
          "value": 2635,
          "unit": "us",
          "threshold": 1000
        },
        {
          "name": "p99.9",
          "value": 5898,
          "unit": "us",
          "threshold": 2000
        },
        {
          "name": "max",
          "value": 11021,
          "unit": "us"
        },
        {
          "name": "ops",
          "value": 8000,
          "unit": "count"
        },
        {
          "name": "block_size",
          "value": 4096,
          "unit": "bytes"
        },
        {
          "name": "span",
          "value": 512,
          "unit": "MiB"
        },
        {
          "name": "o_direct",
          "value": 1,
          "unit": "bool"
        }
      ],
      "advice": "Use a PCIe Gen4x4+ NVMe from the community-vetted list (Samsung 980/990 Pro class), ensure 512-byte LBA on the TrieDB device, and check the drive is not sharing a controller or thermal budget with the OS disk.",
      "elapsed_ms": 4183
    }
  ],
  "disclaimer": "Thresholds are engineering heuristics derived from public Monad docs and community operator data, not official per-metric limits."
}