Server mode and integrations

probescope server runs the exact same probing/detection engine as probescope run, without a terminal UI — built for CI/CD pipelines, automation, and unattended deployments where nothing is watching a screen.

probescope server --hosts 1.1.1.1,8.8.8.8 --terminate 30s

Requires Team or Enterprise (see the pricing page). Every run flag works identically under server — host list, thresholds, --logging, --db, --plugins, --webservice — since both subcommands share one setup path (license/tier checks, config merge, host resolution) and diverge only in how results are consumed: TUI rendering for one, structured logging for the other.

Structured, machine-parseable output

server always logs structured JSON to stdout, never a human-formatted table — a test harness or log pipeline is the intended reader. Two event types matter most:

• event: "state_change" (Info level) — fires only when a host's threshold-confirmed state actually flips (host/addr/ip/method/state: "up"|"down"). This is what a CI/CD pipeline or automation script polls or watches for.
• event: "ping" (Debug level, needs --loglevel debug) — every individual ping, for detailed diagnostics.

Bracketed by an Info-level "start" event and an "exit" event.

Plugins run headlessly too

server evaluates --plugins on the same once-per-second cadence run does — a plugin's terminate(exit_code, message) action works identically, letting a rule end the process (with a specific exit code) the moment a condition is met. This is the mechanism behind "wait for this host to come up, then exit 0" CI/CD gating: a small plugin checks ctx.hosts and calls terminate() once satisfied.

Web console under server

--webservice works under server exactly as it does under run — and since headless mode has no other interactive surface, the web console is the control surface (see the situational awareness topic). Useful for embedding a live status page alongside an automated pipeline.

Logging destinations

--logging file:... works on every tier. --logging syslog://... (Team/Enterprise) sends events to a syslog target over UDP using the standard RFC 5424 format — works with any standard syslog receiver, on every supported platform.

--loglevel

debug/info/warn/error (default info), process-wide — governs both --logging's file/syslog output and server's own stdout event stream with one setting, so filtering never needs to be configured twice.