Skip to content

enumeray connector status

Inspect local journal and native service observations without mutation.

Use when: Check a configured host without initiating probes, repair or recovery.

Role and prerequisites: Configured connector OS account or host administrator. No user profile is loaded.

Terminal window
enumeray connector status --configuration /absolute/connector/runtime.json
Input Meaning and use
--configuration <CONFIGURATION> Saved private host runtime configuration.

Host commands use explicit connector credentials or the private journal and emit JSON results; compute-runner uses only its stdin protocol and directory. User profile and API override options do not apply.

Returns available journal/service evidence. Missing evidence remains unknown and does not prove the previous owning process stopped.

Use setup status or connector diagnostics for authenticated readiness.

Exact syntax, defaults and accepted values
Inspect local journal and native service evidence; performs no probes or repairs
Usage: enumeray connector status [OPTIONS] --configuration <CONFIGURATION>
Options:
--api <API> User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
--configuration <CONFIGURATION> Private connector-host.json for the local installation to inspect
--profile <PROFILE> Named local user API/login profile; host/runner commands use explicit configuration [default: default]
--config <CONFIG> Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
--json Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
--timeout <TIMEOUT> User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
-h, --help Print help

Documentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.