rimba report

Aggregate this repo’s observability metrics into per-command timing stats, designed to be pasted directly into a filed GitHub issue.

rimba can record structured JSONL observability data (a log stream and a compact metrics stream) for every command it runs, written as day-files under os.UserCacheDir()/rimba/. rimba report finds this repo’s day-files, folds every recorded span into per-(command, phase) count/p50/p95/mean duration stats, and prints them alongside an environment header (OS, architecture, CPU count, and rimba version(s) seen in the data).

Works even in a repo without any recorded data, or without .rimba/ initialized at all — it simply finds zero files and reports “no data found”.

What gets recorded. Observability is on by default. The log stream (.log.jsonl, written to the same day-files; read by rimba report only to extract the rimba version(s) seen, never its command-line contents) records every git/gh/exec/hook subprocess this repo’s rimba commands run, including the full command line and, on failure, the subprocess’s captured stderr/output — so a rimba exec command or a post_create/dependency-install command that embeds a credential (e.g. a registry token or a git URL with an embedded password), or whose failure output echoes one, is written verbatim to ~/Library/Caches/rimba (or the platform-equivalent cache dir) and kept for retention_days (default 14). Files are created 0600 (owner-only), but that doesn’t protect against home-directory backups or cache-syncing tools. If this matters for your workflow, set [observability] enabled = false in .rimba/settings.toml, or export RIMBA_NO_OBSERVABILITY to disable it for a single invocation.

Synopsis

rimba report [--json]

Examples

rimba report            # Print the env header and phase timing table
rimba report --json     # Same data as structured JSON

A plain rimba report run prints an environment header followed by a per-(command, phase) timing table:

OS: darwin  Arch: arm64  CPUs: 10  Rimba: 1.9.7
Versions seen in data: 1.9.6, 1.9.7
Unparseable lines: 0

COMMAND     PHASE     COUNT  P50      P95      MEAN
  add       command   12     842.0ms  1210.0ms 903.4ms
  add       deps:api  8      340.0ms  512.0ms  355.1ms
  merge     command   5      612.0ms  780.0ms  655.2ms

If no observability data is found for the current repo, it prints a single line instead:

No observability data found for this repo.

Flags

Flag	Description
--json	Output the environment header and phase stats as structured JSON

Related commands

• rimba doctor · diagnose leftover state from killed worktree operations
• rimba version · print version, commit, build date, and platform info