coldctl agent monitor serve
Serve local metrics, durable failures and optional alert delivery.
ImplementedLocal monitoring; explicit webhook delivery when configured
Syntax
USAGE
coldctl agent monitor serve [OPTIONS]Arguments & options
Examples
Replace configuration names, paths and JOB_ID with values from your installation. Examples are not executed by this page.
CLI
coldctl agent monitor serve --token-env COLDCTL_METRICS_TOKEN --webhook-url-env COLDCTL_ALERT_URL --webhook-token-env COLDCTL_ALERT_TOKENOperational notes
Stop workers and run coldctl init for schema 17. Run the monitor separately from the scheduler using the same --data-dir. Non-loopback listeners require a bearer token and TLS at ingress. HTTPS webhooks use a durable at-least-once outbox; deduplicate event IDs.
Output, placeholders & global flagsView exact CLI help
HELP OUTPUT
Serve Prometheus metrics and durable failure history independently of the worker
Usage: coldctl agent monitor serve [OPTIONS]
Options:
--data-dir <PATH>
Override the OS application data directory
--listen <LISTEN>
[default: 127.0.0.1:9464]
--token-env <TOKEN_ENV>
Bearer token environment reference; required for non-loopback listeners
--poll-seconds <POLL_SECONDS>
[default: 10]
--webhook-url-env <WEBHOOK_URL_ENV>
Environment variable containing the HTTPS alert receiver URL
--webhook-token-env <WEBHOOK_TOKEN_ENV>
--allow-loopback-http
Allow only numeric loopback HTTP for webhook test fixtures
-h, --help
Print help