From 503e53af6cecd60ded73fa1654b73c93a26a99c5 Mon Sep 17 00:00:00 2001 From: DB Lee Date: Thu, 14 May 2026 11:33:52 -0700 Subject: [PATCH] docs(watchdog): clarify first-run results_history is 'missing' until an eval has run Re-validated docs/tutorial-agent-watchdog.md against current develop (330 lines). Most claims line up after the watchdog -> doctor rename: * agentops doctor (CLI), agentops agent serve, and the src/agentops/templates/agent-server/ scaffold all exist with the documented flags. * agentops doctor --categories security and --severity-fail critical are valid and produce findings under the documented Security posture category. * .agentops/agent/report.md and history.jsonl are produced as described, with the source rows the tutorial shows. One small inaccuracy fixed: * Section 1 ('Local dry-run') said 'results-history is the only active source' after the first run. On a fresh workspace - which is what Section 1 has the reader create - results_history is reported as 'missing' (not 'active') because there are no .agentops/results//results.json files yet. Reworded to call out that the source flips to 'ok' once at least one agentops eval run has populated .agentops/results/. Refs #134. --- docs/tutorial-agent-watchdog.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/tutorial-agent-watchdog.md b/docs/tutorial-agent-watchdog.md index 2a7e7d1..428829f 100644 --- a/docs/tutorial-agent-watchdog.md +++ b/docs/tutorial-agent-watchdog.md @@ -38,9 +38,11 @@ agentops doctor ``` The first run produces `.agentops/agent/report.md`. With no -`agent.yaml` the analyzer uses defaults: results-history is the only -active source, Azure Monitor and Foundry control are reported as -`skipped` in the diagnostics block. +`agent.yaml` the analyzer uses defaults: `results_history` is the only +configured source, while `azure_monitor` and `foundry_control` are +reported as `skipped` in the diagnostics block. On a brand-new +workspace `results_history` shows as `missing` until you have at least +one `agentops eval run` under `.agentops/results/` for it to read. ## 2. Wire production telemetry