Dashboard › cli › Distillation
a89c14f7-13a3-4b3d-8131-c0d551e90803["lore_tm_v1_lVlWRYU4VOh6-d-HJsFQlkNYFqhoEzpYpLRD5xT9rd0"]
/home/byk/.local/share/opencode/tool-output/tool_0831128aa001bpCEBxhl07Kua5.fullDescription while structured examples remained [] for the displayed commands: sentry trace list, sentry trace view, sentry trace logs, sentry trial list, sentry trial start, sentry init, sentry info, sentry local serve, sentry local run, sentry api, and sentry schema.sentry trace list metadata reported positional [<org/project>]; aliases t→period, n→limit, q→query, s→sort, f→fresh, c→cursor, v→verbose; defaults limit="25", sort="date", period="7d", fresh=false; and JSON fields in order: trace, id, transaction, timestamp, transaction.duration, project. Its prose examples were: 1. sentry trace list; 2. sentry trace list --limit 50; 3. sentry trace list --sort duration; 4. sentry trace list --period 24h; 5. sentry trace list -q "transaction:GET /api/users".sentry trace view metadata reported positional <org/project/trace-id...>, aliases f→fresh, w→web, v→verbose, web=false, full=false, and spans="3"; accepted target forms were <trace-id>, <org>/<project>/<trace-id>, or <project> <trace-id>, with a 32-character hexadecimal trace ID.sentry trace logs metadata reported positional <org/project/trace-id...>; defaults period="14d", limit="100", sort="newest", web=false, fresh=false; aliases f→fresh, w→web, t→period, n→limit, q→query, s→sort, v→verbose; and prose examples for a raw trace ID, myorg/<trace-id>, myorg/backend/<trace-id>, --period 7d, and --json.sentry trial list metadata reported positional [<org>], alias v→verbose, and JSON fields in order: category (string), startDate (string | null), endDate (string | null), reasonCode (number), isStarted (boolean), lengthDays (number | null). Its prose examples were sentry trial list, sentry trial list my-org, and sentry trial list --json.sentry trial start metadata reported positional <name> [<org>]; valid trial names were seer, replays, performance, spans, profiling, logs, monitors, uptime, and plan; plan opens the billing page for a Business plan trial. Prose examples were sentry trial start seer, sentry trial start seer my-org, sentry trial start replays, sentry trial start plan, and sentry trial start --json seer.sentry init metadata reported positional [<target>] [<directory>]; flags yes=false, dry-run=false, variadic features, optional team, optional app, and tui=true; aliases n→dry-run, y→yes, t→team, v→verbose. Supported features were errors,tracing,logs,replay,profiling,crons,agent-tracing,mcp-observability; prose examples were sentry init, sentry init acme/, sentry init acme/my-app, sentry init my-app, sentry init acme/my-app ./my-project, and sentry init ./my-project.sentry info metadata exposed --config-status-json (machine-readable configuration/auth status and always exits 0) and --no-defaults (verify authentication without requiring default org/project); it had no positionals and structured examples was [].sentry local serve metadata reported defaults port="8969", host="localhost", quiet=false, format="human", attributes=false; repeatable filter values error, transaction, log, or ai; aliases p→port, H→host, q→quiet, f→filter, F→format, a→attributes, v→verbose.sentry local run metadata reported positional <command...>; defaults port="8969", host="localhost", verify=false, timeout="0", format="human", attributes=false; aliases p→port, f→filter, V→verify, t→timeout, F→format, a→attributes, v→verbose. It injects SENTRY_SPOTLIGHT, framework-prefixed client variants such as NEXT_PUBLIC_ and VITE_, and SENTRY_TRACES_SAMPLE_RATE=1; --format json streams versioned NDJSON, and --verify defaults to a 30-second timeout when no explicit timeout is supplied. Prose examples were sentry local run -- npm run dev and sentry local run -- python manage.py runserver.sentry api metadata reported required positional <endpoint> relative to /api/0/; defaults method="GET", silent=false, verbose=false, dry-run=false; aliases X→method, d→data, F→field, f→raw-field, H→header, n→dry-run. Supported body forms were inline JSON via --data/-d, file or stdin via --input/-i, typed fields via --field/-F (key=value, key[sub]=value, key[]=value, key[]), and unparsed string values via --raw-field/-f. Its 5 prose examples covered organizations/, resolving issue 123 via -F and via -d, setting options[sampleRate]=0.5, and adding user[email]=user@example.com.sentry schema metadata reported optional variadic positional <resource...>, all=false, optional search, aliases q→search and v→verbose; prose examples in order were: 1. sentry schema; 2. sentry schema issues; 3. sentry schema issues list; 4. sentry schema --all; 5. sentry schema --search monitor.SENTRY_AUTH_TOKEN (API token; example sntrys_YOUR_TOKEN_HERE; stored OAuth normally takes priority); 2. SENTRY_FORCE_ENV_TOKEN (example 1; makes SENTRY_AUTH_TOKEN/SENTRY_TOKEN override stored OAuth); 3. SENTRY_ORG (example my-org); 4. SENTRY_PROJECT (example my-org/my-project; org/project causes SENTRY_ORG to be ignored); 5. SENTRY_DSN (example https://key@o123.ingest.us.sentry.io/456); 6. SENTRY_HOST (example https://sentry.example.com, default https://sentry.io, takes precedence over SENTRY_URL); 7. NO_COLOR (example 1, respected when SENTRY_PLAIN_OUTPUT is unset); 8. SENTRY_LOG_LEVEL (example debug, default info, valid values error, warn, log, info, debug, trace, with CLI flags taking precedence).--json (Output as JSON (with --fields to select)); 2. --fresh/-f (Bypass cache and fetch fresh data); 3. --verbose/-v (Enable debug logging); 4. --help (Show help for a command); 5. --version (Show version).