Forwarding command
Usebeacon endpoint asymptote to generate the content pack that forwards Beacon endpoint events to Asymptote’s managed ingest service. The pack keeps Beacon as a local JSONL producer: Vector tails the runtime and inventory logs and POSTs gzip-compressed NDJSON batches over HTTPS with a per-device key.
This is the one destination that sends telemetry to an Asymptote-run endpoint. It is opt-in and revocable: nothing is forwarded until a member of your Asymptote organization has approved the device in the browser and Vector has been started with the resulting key. beacon endpoint connect performs that enrollment and runs the forwarder as a service; the commands on this page generate the same files for running or inspecting the forwarder by hand.
Beacon does not store the device key in its own configuration. The key lives in a 0600 JSON secrets file that Vector reads through its secret backend, so it appears in neither vector.toml nor the process environment.
Command syntax
Commands
beacon endpoint asymptote print-config
Print the Vector forwarding config for the configured runtime log.
beacon endpoint asymptote install-pack
Write the forwarding pack to a directory.
beacon endpoint asymptote validate
Write and describe a Beacon Asymptote validation event.
Runtime log paths
The inventory log is the sibling
inventory_state.jsonl in the same directory.
beacon endpoint asymptote print-config
beacon endpoint asymptote print-config prints the Vector configuration that tails the selected Beacon runtime and inventory logs and posts them to the ingest service.
Print the configuration
Flags
beacon endpoint asymptote install-pack
beacon endpoint asymptote install-pack writes the forwarding pack to a directory.
Generate the pack
README.mdwith the wire contract, what leaves the machine, and how to run Vector by hand.vector.toml, the forwarder. Its startup healthcheck calls the authenticated/v1/ingest/health, so a revoked key is reported when Vector starts.asymptote-ingest-smoke-test.sh, a one-shot credential check plus a manual POST of the log tail.sample-event.jsonlwith Beacon endpoint events in the shape the service accepts.
Examples
Generate a pack for a system-mode deployment
Run the forwarder by hand
Flags
beacon endpoint asymptote validate
beacon endpoint asymptote validate writes a Beacon validation event to the runtime JSONL log and prints the expected fields plus the credential check to run.
Run the validation check
Beacon endpoint Asymptote validation event.
Expected validation fields:
200 means the key is valid; 401 means it was revoked, expired, or the approving user is no longer a member of the organization.
Flags
Related
Asymptote managed forwarding
Wire contract, what leaves the machine, revocation, and offline behavior.
Log forwarding
Review forwarding patterns and validation steps.
Endpoint agent
Install and inspect the local endpoint agent.
Endpoint event schema
Review normalized Beacon JSONL fields and example events.

