autonomy support-bundle generate

Generate a support bundle archive (.tar.gz)

Synopsis

Collects diagnostic information and writes it to a .tar.gz archive.

Bundle contents: manifest.json — collection status for every section, timestamps, and errors system_info.json — OS, architecture, Go version, hostname build_info.json — binary version and build metadata (commit, VCS settings) config_redacted.yaml — effective config with secrets redacted (requires –config-file) ha_status.json — HA cluster status snapshot (requires –orchestrator-url) audit_recent.json — most recent 50 audit records (requires –audit-dir) logs/autonomy.log — recent log lines tailed from the specified file (requires –log-file)

Secret redaction: identity.fleet_salt is replaced with “”. postgres_url passwords are replaced with “REDACTED”. Certificate file paths are preserved (paths are not secrets; contents are not collected).

Errors from individual collectors are non-fatal: the bundle is written with all available data. Inspect manifest.json for any collection failures.

Usage

autonomy support-bundle generate [flags]

Options

      --audit-dir string          audit storage directory (env: AUTONOMY_AUDIT_DIR)
      --config-file string        path to autonomy.yaml for effective-config collection
      --log-file string           path to log file to tail and include in the bundle
      --log-lines int             number of recent log lines to include from --log-file (default 500)
      --orchestrator-url string   orchestrator base URL for status snapshots (env: AUTONOMY_ORCHESTRATOR_URL)
      --output string             output path for the bundle archive (default: autonomy-bundle-<timestamp>.tar.gz)

See also