The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
update docs
Justin D'Souza21d61dd844bc
diff --git a/cli/beacon/internal/endpoint/s3/pack/README.md b/cli/beacon/internal/endpoint/s3/pack/README.mdindex 346e1125..be8d0488 100644--- a/cli/beacon/internal/endpoint/s3/pack/README.md+++ b/cli/beacon/internal/endpoint/s3/pack/README.md@@ -140,8 +140,8 @@ under `${BEACON_S3_PREFIX}/inventory/date=.../`.When an event contains canonical token or cost attribution under`gen_ai.usage`, the Vector template preserves the original nested payload and-also emits top-level analytics fields for downstream warehouses such as-ClickHouse: `input_tokens`, `output_tokens`, `cache_read_input_tokens`,+also emits top-level analytics fields for downstream warehouses:+`input_tokens`, `output_tokens`, `cache_read_input_tokens`,`cache_creation_input_tokens`, `reasoning_output_tokens`, and `cost_usd`.`cost_usd` is runtime-reported only; Beacon does not derive cost from localpricing tables.diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 012ca242..502f4382 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -13,7 +13,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.### v0.0.73 · June 21, 2026-- **S3 token and cost analytics fields** · The S3 Vector forwarding template now preserves canonical `gen_ai.usage` and also emits top-level `input_tokens`, `output_tokens`, `cache_read_input_tokens`, `cache_creation_input_tokens`, `reasoning_output_tokens`, and `cost_usd` fields so downstream warehouses such as ClickHouse can persist usage attribution reliably.+- **S3 token and cost analytics fields** · The S3 Vector forwarding template now preserves canonical `gen_ai.usage` and also emits top-level `input_tokens`, `output_tokens`, `cache_read_input_tokens`, `cache_creation_input_tokens`, `reasoning_output_tokens`, and `cost_usd` fields so downstream warehouses can persist usage attribution reliably.- **Managed onboarding docs** · Added an onboarding page for managed ingest setup and clarified the S3 forwarding path for teams wiring Beacon endpoint telemetry into managed analytics.- **Observe contract conformance** · Added cross-language contract checks to keep Beacon event constants aligned between the Go schema package and the TypeScript SDK.diff --git a/docs/images/asymptote_dashboard_okta_connector.png b/docs/images/asymptote_dashboard_okta_connector.pngnew file mode 100644index 00000000..a1b365beBinary files /dev/null and b/docs/images/asymptote_dashboard_okta_connector.png differdiff --git a/docs/images/okta_token_generation.png b/docs/images/okta_token_generation.pngnew file mode 100644index 00000000..25ea5ba7Binary files /dev/null and b/docs/images/okta_token_generation.png differdiff --git a/docs/log-forwarding/s3.mdx b/docs/log-forwarding/s3.mdxindex 19467ddc..e4d47357 100644--- a/docs/log-forwarding/s3.mdx+++ b/docs/log-forwarding/s3.mdx@@ -117,7 +117,7 @@ In managed deployments, provide `BEACON_S3_BUCKET`, optional `BEACON_S3_PREFIX`,The template expects a Vector version with the `file` source, `remap` transform, and `aws_s3` sink. It parses each Beacon JSONL line and re-encodes the original Beacon event as JSON with newline-delimited framing so S3 receives one Beacon event per line, without a Vector wrapper.-When a runtime event includes canonical token or cost attribution under `gen_ai.usage`, the generated Vector config preserves that nested payload and also emits top-level analytics fields for downstream warehouses such as ClickHouse: `input_tokens`, `output_tokens`, `cache_read_input_tokens`, `cache_creation_input_tokens`, `reasoning_output_tokens`, and `cost_usd`. `cost_usd` is runtime-reported only; Beacon does not derive cost from local pricing tables.+When a runtime event includes canonical token or cost attribution under `gen_ai.usage`, the generated Vector config preserves that nested payload and also emits top-level analytics fields for downstream warehouses: `input_tokens`, `output_tokens`, `cache_read_input_tokens`, `cache_creation_input_tokens`, `reasoning_output_tokens`, and `cost_usd`. `cost_usd` is runtime-reported only; Beacon does not derive cost from local pricing tables.The template uses date-partitioned `key_prefix`, `filename_time_format = "%s"`, and `filename_append_uuid = true` so production forwarding does not overwrite previous S3 objects. It also sets `compression = "gzip"`, `content_encoding = "gzip"`, and `content_type = "application/x-ndjson"`.diff --git a/docs/manage/connect-okta.mdx b/docs/manage/connect-okta.mdxindex 3ed69f2e..eda16443 100644--- a/docs/manage/connect-okta.mdx+++ b/docs/manage/connect-okta.mdx@@ -17,6 +17,10 @@ Connect Okta from the Asymptote dashboard to automatically populate the users, g5. Enter your Okta org URL.6. Enter your Okta API token.+<Frame caption="Use the Okta connector setup flow in the Asymptote dashboard to enter your Okta org URL and API token.">+ <img src="/images/asymptote_dashboard_okta_connector.png" alt="Asymptote dashboard Okta connector setup form." />+</Frame>+After the connector is authorized, Asymptote automatically syncs Okta data into the users, groups, and devices tabs in the dashboard.## Generate an Okta API Token@@ -28,4 +32,8 @@ Create the Okta API token from the Okta Admin Console:3. Select **Tokens**.4. Click **Create token**.+<Frame caption="Generate the API token from the Okta Admin Console before returning to the Asymptote connector setup.">+ <img src="/images/okta_token_generation.png" alt="Okta Admin Console API token generation screen." />+</Frame>+Copy the generated token and paste it into the Okta connector setup flow in Asymptote.diff --git a/docs/manage/onboarding.mdx b/docs/manage/onboarding.mdxindex faa491ea..3f6f69e8 100644--- a/docs/manage/onboarding.mdx+++ b/docs/manage/onboarding.mdx@@ -3,3 +3,14 @@ title: "Onboarding"description: "Onboarding guides for Asymptote managed connectors."tag: "Enterprise"---++Use these guides to connect managed data sources during Asymptote onboarding.++<Columns cols={2}>+ <Card title="Connect Okta" icon="users" href="/manage/connect-okta">+ Populate users, groups, and devices from Okta.+ </Card>+ <Card title="Configure S3 Data Connector" icon="bucket" href="/manage/configure-s3-data-connector">+ Grant read-only access for managed event ingestion from S3.+ </Card>+</Columns>