CLI
autotel-cli provides an interactive setup wizard, diagnostics, incremental feature additions, and telemetry investigation commands.
Installation
Section titled “Installation”npm install -g autotel-cli# ornpx autotel <command>Commands
Section titled “Commands”autotel init
Section titled “autotel init”Interactive setup wizard:
# Interactive modenpx autotel init
# Use defaultsnpx autotel init --yes
# Use a quick presetnpx autotel init --preset node-datadog-pino
# Dry runnpx autotel init --dry-runQuick presets:
node-datadog-pino— Node.js + Datadog + Pino loggingnode-datadog-agent— Node.js + Datadog Agent (local dev)node-honeycomb— Node.js + Honeycombnode-otlp— Node.js + Generic OTLP endpoint
autotel doctor
Section titled “autotel doctor”Run diagnostics on your setup:
npx autotel doctor # Run all checksnpx autotel doctor --json # Machine-readable outputnpx autotel doctor --fix # Auto-fix resolvable issuesautotel add <type> <name>
Section titled “autotel add <type> <name>”Add components incrementally:
npx autotel add backend datadognpx autotel add subscriber posthognpx autotel add plugin bigquerynpx autotel add platform cloudflareautotel investigate surface
Section titled “autotel investigate surface”The CLI can query and diagnose telemetry directly (same backend model as autotel-mcp), returning one JSON document per invocation.
# backend health + signal availabilitynpx autotel healthnpx autotel capabilities
# discoverynpx autotel discover servicesnpx autotel discover trace-fieldsnpx autotel discover log-fields
# traces / spans / logs / metricsnpx autotel query traces --service-name checkout --error-only --limit 20npx autotel query spans --service-name checkout --operation-name db.querynpx autotel query logs --trace-id <traceId>npx autotel query metrics --service-name checkout
# incident triagenpx autotel diagnose anomalies --service checkoutnpx autotel diagnose root-cause <traceId>npx autotel correlate trace <traceId>All backend-touching commands accept:
--backend collector|jaeger|tempo|prometheus|loki|stack|auto|fixture--jaeger-base-url <url>--tempo-base-url <url>--prometheus-base-url <url>--loki-base-url <url>--collector-port <n>--fixture-path <path>Use --output-file <path> to persist command JSON and --no-secrets-in-output to redact secret-shaped values.
Examples
Section titled “Examples”See any example app — autotel init generates the instrumentation.ts file used across all examples.
autotel codemod trace <path>
Section titled “autotel codemod trace <path>”Wrap functions with trace():
npx autotel codemod trace ./srcRelated
Section titled “Related”- MCP — the
autotel-mcpserver this CLI investigate surface mirrors. - Claude Code Skill — using these commands from a Claude skill workflow.
- Devtools — local OTLP receiver UI. Run it with
npx autotel-devtools(notnpx autotel dev tools).