From 1cc53a7c527ee566ce51590c621042c4057a4be3 Mon Sep 17 00:00:00 2001 From: Telm Olivella Date: Mon, 9 Nov 2026 14:42:46 +0100 Subject: [PATCH] docs(platform): sync with develop changes Co-Authored-By: Claude Opus 5.5 --- platform/event-schema.mdx | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/platform/event-schema.mdx b/platform/event-schema.mdx index 70098c67..d094be82 100644 --- a/platform/event-schema.mdx +++ b/platform/event-schema.mdx @@ -95,6 +95,24 @@ There is **no `ip` column**. Rules that previously grouped by IP now use **sessi | `protocol` | `request_protocol` | `llm` \| `mcp` \| `a2a` | | `policy_id` / `policy_name` | `policy_id` / `policy_name` | Evaluating policy | | `latency.detectors_ms` / `latency.overhead_ms` | `latency` JSON | Detector timing | +| `api_key.id` / `api_key.masked` | `api_key_id` / `api_key_masked` | The collector key that authenticated the call, in display form (`tgk_…6c22`), never the key itself. Empty for any other authentication, including traffic TrustGate forwards. Shown as **API key** in Activity. | + +--- + +## Raw record fields shown in Activity + +The raw store also keeps a few short fields derived from the body, so +**Activity** can show them without loading every payload. Like the bodies, they +never reach the metadata stream. + +| Field | Product | Notes | +|---|---|---| +| `request_preview` | TrustGate | The start of the request, at most 200 characters. For LLM calls, the last user turn, so an agent loop shows the person's prompt, not tool output. For MCP `tools/call`, `tool(first string argument)`, skipping arguments named like credentials. Shown in the **Request** column and as the **First prompt** of a conversation. | +| `preview` | TrustGuard | The start of the evaluated content, at most 200 characters: the latest message that is not a system prompt, or the tool names of a tool list. Credentials are redacted first. Bodies over 1 MiB get none, and Activity leaves the **Request** column empty when DLP masked a value in the event. | +| `record_hash` | TrustGuard | Hex SHA-256 of the stored record (version `trustguard.record.v1`), shown as **Integrity** in Activity. Records are not chained to each other. | + +On hybrid deployments the bodies stay in your data plane, so there is no preview +and Activity hides the **Request** column. ---