Logging & telemetry

The Logging & Telemetry page controls the logging and telemetry that power the Observe pages, from tool-call traces to agent session capture. Open it from Settings > Logging & Telemetry in the dashboard.

Access requirements

Viewing this page requires the org:read scope, so both default Admin and Member roles can see current settings. Changing any toggle or configuration requires the org:admin scope, which only the default Admin role holds.

Logging toggles

The page presents a set of toggle rows that control what the platform records.

• Enable Logs records tool-call traces and telemetry. Turning this off also turns off dependent settings.
• Upload Skill Content uploads each skill’s SKILL.md content at activation so captured skills can be inspected. When disabled, the platform receives only skill names, source details, hashes, users, and hostnames at activation.
• Record Tool I/O stores the inputs and outputs of tool calls. Stored payloads may expose sensitive data, so enable it deliberately. This setting requires Enable Logs to be on; turning logs off cascades this setting off as well.
• Agent Session Capture captures prompts and responses from Cursor, Claude Code, Codex, and other assistants. Captured sessions appear in Agent Sessions. This setting also requires Enable Logs to be on.
• Fail Open During Outages lets tool calls proceed when the platform is unreachable instead of blocking them (blocking is the default). Blocking policies go unenforced during the outage; events are still recorded and scanned after recovery, and invalid credentials always block.
• Hook Browser Sign-In lets hook plugins sign users in through the browser so events record under their own identity. When off, plugins use the organization key or explicitly configured credentials.

AI integrations

Provider compliance and admin APIs (Cursor, Anthropic, OpenAI) connect on their own settings page — see AI Integrations. They’re optional; the platform works with basic instrumentation alone.

OTEL forwarding

The OTEL Forwarding section forwards a copy of every OTEL payload received on the hooks endpoint to an external collector. Enable forwarding turns delivery on, the Endpoint URL field sets the destination, and the Headers list attaches custom headers to forwarded requests (Add header to add rows). Header values are encrypted at rest and never returned by the API; saved values are preserved on subsequent edits.