Skip to main content

​
Command overview

beacon endpoint config inspects and safely updates the local Beacon endpoint configuration.
Command syntax
Use this command group when you need to review the effective endpoint configuration or validate config file contents without reinstalling the endpoint agent.

​
Commands

show

Print endpoint configuration with secrets redacted.

validate

Validate endpoint configuration and destination settings.

​
Flags

​
beacon endpoint config show

beacon endpoint config show prints the endpoint configuration with secrets redacted.
Manage endpoint configuration
Splunk HEC tokens and other secret destination values are not printed. Use this command before support handoffs or diagnostics collection when you need to confirm paths, ports, harnesses, and destination settings.

​
Examples

Show per-user endpoint config:
Show per-user endpoint config
Show system endpoint config:
Show system endpoint config

​
beacon endpoint config validate

beacon endpoint config validate validates the endpoint configuration file.
Run the validation check
Validation checks endpoint and destination configuration. For example, Splunk HEC and Falcon LogScale HEC forwarding require both an endpoint URL and token when configured.

​
Examples

Validate per-user endpoint config:
Validate per-user endpoint config
Validate system endpoint config:
Validate system endpoint config

​
Managed ingest block

When the endpoint is connected to Beacon managed ingest, config.json carries a non-secret managed_ingest block: beacon endpoint connect writes the block and beacon endpoint disconnect clears it. It never holds the device key, which lives only in asymptote/vector-secrets.json, and it survives re-running beacon endpoint install.

Endpoint install

Configure endpoint telemetry and collector service files.

Diagnostics bundle

Collect redacted endpoint support artifacts.