Retention and redaction
Beacon can write supported prompt, command, tool, file, approval, policy, and runtime context when a configured source runtime emits it. Before endpoint events are written to local JSONL or forwarded through configured destinations, Beacon applies redaction, sanitization, truncation, and event-size limits.Content handling
What is redacted
Redaction runs on retained text (prompts, command output, diffs, tool arguments and results, reasons) and on structured payloads. Each match is replaced with[REDACTED], keeping the label in front of it, so token=abc becomes token=[REDACTED]. Redaction runs before truncation, so a cut never leaves part of a secret behind.
Redaction is pattern-based. A credential with no label and no recognizable shape, such as a bare random password, is not detected, so treat retained content as sensitive. Metadata-only forwarding is the control for keeping content off Asymptote managed ingest entirely.
Prompt event example
Prompt content is included only when the source runtime emits it. Secret-like values are redacted before the event is written:Command event example
Command events can include normalized tool and command context, with truncation metadata when fields exceed limits:Forwarding implications
Content handling is applied before events are written toruntime.jsonl.
File-based destinations such as Wazuh, Elastic/Filebeat, Datadog Agent custom
log collection, Sumo Logic forwarding, Rapid7 forwarding, Microsoft Sentinel
forwarding, AWS S3 Vector forwarding, Google Cloud Storage Vector forwarding,
and customer-managed shippers read the resulting local JSONL. Supported cloud
agents upload a compressed snapshot of their sandbox-local JSONL directly to
customer-managed GCS or S3. Splunk HEC and Falcon LogScale HEC forwarding
receive the same normalized collector output according to the configured
endpoint pipeline. Asymptote managed ingest, when a device has been connected,
forwards new runtime and inventory lines in Standard mode exactly as stored
locally, so the same retention and redaction settings govern what reaches the
Asymptote dashboard. Metadata-only mode adds a local Vector transform that
removes retained text, tool arguments/results, tool definitions, retrieval
queries and documents, approval and policy reasons, command output, raw fields,
diffs, inventory content, and MCP definitions before buffering or upload while
preserving stable metadata, hashes, counts, and token usage.
Each retained string is capped at 4 KB (DefaultStringLimit in
pkg/asymptoteobserve/privacy.go) before it is written, so text past that point
in a long tool output, command output, or diff is never forwarded or searchable
downstream; the event carries field_truncated and content.truncated instead.
Review runtime scope, artifact access, destination permissions, and downstream retention before rollout so retained content matches your approved telemetry policy.
Related
Schema examples
Inspect endpoint event examples and content fields.
Endpoint install
Configure endpoint telemetry and collector service files.