tetrate agentrouter doctor

Troubleshoot Agent Router deployments

Usage:
  tetrate agentrouter doctor [identity.json] [flags]
  tetrate agentrouter doctor [command]

Available Commands:
  dump-crds               Dump the installed CRDs the release requires, as YAML

Flags:
      --bundle string                Bundle upload policy: always (build and upload a support bundle every run), on-transition (upload the report only; build a bundle when the management plane requests one), never. Default: on-transition. TARE_DOCTOR_SKIP_BUNDLE=true is a deprecated alias for never.
      --context string               Kubernetes context override
      --dataplane-namespace string   Data plane namespace to inspect (default "tars-dataplane")
      --fail-on string               Severity threshold that fails the run: error (default; ERROR issues or findings, or a False condition, fail), warning (ERROR or WARNING issues or findings fail), none (never fail on findings) (default "error")
      --log-scan-window duration     Only pod log lines written within this window count toward log-signature findings; older lines in the tail are ignored so a resolved error stops being reported (default 1h0m0s)
      --mcp-churn-threshold int      Retirement count within --mcp-churn-window above which the MCP route-churn check warns (default 10)
      --mcp-churn-window duration    Window over which to count MCP RouteDeployment retirements for the churn check (default 15m0s)
      --only string                  Run a single named check (e.g. mp-connectivity, helm-releases, identity, gateway, mcp-churn, feature-config) or every individually runnable check in a category (platform-health, config-validity, connectivity-trust, traffic-usage, drift-detection) instead of the full pipeline; does not upload a bundle. Checks that only run as part of the full pipeline (collectors and barrier-fed analyzers) are not included in a category run.
  -o, --output string                Output format: text, json, or sarif (SARIF 2.1.0 log of the typed findings; the management plane still receives the JSON report) (default "text")
      --release-name string          Helm release name to inspect (default "tars")
      --system-namespace string      System namespace to inspect (default "tars-system")
      --tier string                  Run one process boundary instead of everything: fast (the every-tick checks with the stats-only Envoy view; reads no pod logs, uploads the report only), deep (every check and the bundle decision; the log-signature scan runs on ticks that send a bundle), events (install-event reconcile and forward only; no health checks). Default: everything in one run (deep plus events).
      --timeout duration             Timeout for cluster health checks (default 5m0s)
      --upload-timeout duration      Timeout for bundle zip build and POST to the management plane when using identity (0 = no extra deadline beyond command context) (default 5m0s)
      --verbose                      Include detailed issue output

Global Flags:
  -q, --quiet   Suppress progress output; only errors and the final summary go to stderr

Use "tetrate agentrouter doctor [command] --help" for more information about a command.