clawker monitor
Manage local observability stackSynopsis
Commands for managing the local observability stack. The monitoring stack provides local telemetry visualization for coding-agent harness sessions using OpenTelemetry Collector + OpenSearch (logs + traces) + OpenSearch Dashboards + Prometheus (metrics). Available commands: init Scaffold monitoring configuration files up Start the monitoring stack reload Apply this project’s monitoring extensions to the running stack down Stop the monitoring stack status Show monitoring stack status extensions List resolvable monitoring extensions Monitoring extensions are observability loadouts (OpenSearch index + ingest pipelines + dashboards + collector routing). A project selects them by name in its clawker.yaml (monitor.extensions); they resolve from the embedded
floor, a loose .clawker/monitoring/<name>/ directory, or an installed bundle, and
are seeded onto the stack by ‘monitor up’ (or applied to a running stack by
‘monitor reload’).
Examples
Subcommands
- clawker monitor down - Stop the monitoring stack
- clawker monitor extensions - List resolvable monitoring extensions and their provenance
- clawker monitor init - Scaffold monitoring configuration files
- clawker monitor reload - Apply this project’s monitoring extensions to the running stack
- clawker monitor status - Show monitoring stack status
- clawker monitor up - Start the monitoring stack
Options
Options inherited from parent commands
See also
- clawker - Run coding agents in secure Docker containers with clawker