Configure audit, retention and telemetry
Find who changed a factory, set how long operational data is retained, and verify that a collector receives the organization's traces and metrics.
Open the organization in CodeBook and choose Settings as an organization owner or admin. These settings apply across its factories. Manage people, identity and model access in Bookbag SSO.
Find or export an audit event
Open Audit log and filter by action, who performed it, text or date range. For example, after someone switches off a factory plugin, narrow the dates to that day and look for the plugin change. The trail covers connector writes, token changes, factory and policy changes and merges performed by CodeBook. Use CSV for a spreadsheet or JSON for automated inspection.
CodeBook records local events and forwards them to Bookbag. If the shared service is unavailable, the page identifies the local CodeBook trail. An empty search there is not evidence that nobody changed an account at SSO. Narrow your filters or check the shared trail after forwarding resumes.
Set data retention
Open Data retention. Set a policy separately for run transcripts, saved conversations and model-call records. Keep the default, specify a duration from 1 to 3,650 days, or keep records until deleted. Review the affected data type and confirm when shortening a policy. The scheduled cleanup applies the change; saving does not delete records immediately.
With defaults, run transcripts use the deployment's transcript retention (365 days unless changed), saved conversations use the person's choice or 365 days, and model-call records use 90 days. An organization limit can shorten how long a person's conversations saved in that organization are kept. It does not change a conversation saved without an organization.
Connect an OpenTelemetry collector
- Prepare a collector that accepts OTLP over HTTP with JSON. Obtain its HTTPS endpoint and any authentication headers. In Settings → Telemetry, enter the endpoint and headers; the export starts off. Changing an existing secret header requires removing it and adding its replacement.
- Choose the data you need. Traces describe runs; metrics cover usage such as tokens, costs, outcomes, queue time and duration. Prompt and code content is excluded by default. Enabling content asks for confirmation because the collector will then receive it.
- Save the configuration and use Send a test. Check the test result and the collector itself. Enable the export when ready, then confirm a real run appears for the intended organization.
- If delivery stops, review the last error, failure count and retry time. After 20 consecutive failures the export turns off. Fix the endpoint or headers, send another test, and explicitly switch it back on. Private network destinations require the deployment operator to allow that host.
Choose models and prices
The organization's allowed models and provider credentials come from Bookbag SSO. A disallowed model cannot run in a fixed policy, a fallback chain or automatic routing. If a required model is absent, check its organization access before editing the factory. See model routing and work orders for how the approved rates and limits affect new work.