Sources and connectors
Sources is where records come from. Three kinds exist:
- SDKs push records from inside your agents. They appear as sources named
sdk-pythonandsdk-typescriptonce the first record arrives. Nothing to configure here beyond an ingest key. - OpenTelemetry collectors push traces to the endpoint shown on the page. One trace becomes one decision. Attributes to set.
- Pull connectors fetch from a provider on a schedule: Langfuse and the Anthropic Compliance API today.
Connected sources
Section titled “Connected sources”Each card shows the source, its kind and assurance level, records ingested, the last run and its status, and the schedule. Sync now runs it immediately. Runs opens the history: when each run started and finished, records seen and new, and the error if it failed. A missing secret fails a run with a readable error and leaves the source usable.
Adding a connector
Section titled “Adding a connector”Engineers, admins and owners can add one. Choose the connector, fill in what it needs, then Test: Stratl connects with the credentials and reports whether it could reach the provider and how much recent data it sees. Save creates the source and schedules it.
Secrets are never typed into Stratl. A connector takes a secret reference such as env:LANGFUSE_SECRET_KEY (an environment variable on the API server) or aws-sm:arn:… (a secret in AWS Secrets Manager). Stratl resolves it at use and stores only the reference.
| Connector | Needs | Records |
|---|---|---|
| Langfuse | Base URL (cloud EU, cloud US or self-hosted), public key, secret reference to the secret key, optional environment filter | One decision per trace; generations become model calls, tool observations become tool calls; business facts from stratl.* metadata. Details. |
| Anthropic Compliance API | A Compliance Access Key (Claude Enterprise) by secret reference | One decision per Claude Code, Cowork, Claude Science, Microsoft 365 or Chrome session, with content fingerprinted and provenance markers kept. Details. |
Every pull connector records at assurance level observed: it saw what the provider reported, no more.
Pause, reset, remove
Section titled “Pause, reset, remove”Edit a source to disable it (the schedule stops; nothing is deleted) or to reset its cursor (the next run starts from the initial lookback again; ingest is idempotent, so replays never duplicate records). Removing a source deletes the source and its run history; the records it produced stay, because they are evidence.