Skip to content

cloudtaser-cli beacon status

Fetches the stable /readyz endpoint of a cloudtaser-beacon. A healthy default install succeeds even when its opt-in /metrics endpoint is disabled. When metrics are available, status adds cluster, ring, match, forwarding, and split-brain details as optional enrichment.

The default address http://localhost:8080 targets the beacon's own health server for on-host troubleshooting. That listener is intentionally loopback plain HTTP; remote plain-HTTP targets still require --insecure.

Scheme handling: - explicit https://... — always allowed - explicit http://127.0.0.1 / http://localhost — always allowed (loopback on-host default, no --insecure needed) - explicit http:// — requires --insecure - scheme-less host:port — prefixed https:// unless --insecure is set

Usage

cloudtaser-cli beacon status [flags]

Examples

# On the beacon host (http://localhost:8080, loopback default)
  cloudtaser-cli beacon status

  # Remote beacon (scheme-less -> https://)
  cloudtaser-cli beacon status --address beacon.example.com:8080

  # Legacy plain-HTTP remote dev beacon
  cloudtaser-cli beacon status --address beacon.example.com:8080 --insecure

  # JSON for automation
  cloudtaser-cli beacon status --address beacon.example.com:8080 --json

Flags

Flag Type Default Required Description
--address string http://localhost:8080 no beacon health server URL — defaults to loopback plain-HTTP http://localhost:8080 for on-host troubleshooting (pass https://... or host:port for remote TLS beacons, --insecure for remote plain-HTTP)
--help, -h bool false no help for status
--insecure bool false no accept plain-HTTP beacon URLs — scheme-less addresses are prefixed http:// and explicit http:// URLs are allowed
--json bool false no emit parsed state as JSON (for automation)
--metrics-address string (empty) no optional metrics listener URL for enrichment (default: try /metrics on --address; disabled/unavailable metrics do not fail status)
--timeout duration 5s no HTTP timeout for readiness and optional metrics fetches
--token-file string (empty) no path to a file containing the bearer token for protected health/metrics topology, or '-' for stdin

All commands