Documentation
¶
Overview ¶
Command e2a-prober runs the e2a critical-path self-test (internal/selftest) against a live instance, four ways:
seed — idempotently provision the synthetic system-class probe account,
agent, API key, and webhook (prints credentials to capture in env).
validate — pre-flight: config parses, DB reachable, migrations applied,
probe identity present. No round-trip. (vault-diagnose style.)
run-once — run the battery once, exit 0 (all pass) / 1 (any fail). For CI.
serve — loop every interval; host /sink, /healthz, /metrics, /status for
the continuous monitor and the deploy bake-gate.
The probe runs under a system-class account, so its traffic is never metered (usage.PolicyFor); self-send uses loopback (no egress); inbound is synthetic mail to the probe agent (no real recipient, no owner notification).
Click to show internal directories.
Click to hide internal directories.