> For the complete documentation index, see [llms.txt](https://docs.controltheory.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/sources.md).

# Sources

Get logs flowing!

A **Source** is a connection to an external platform that brings logs, metrics and traces into Dstl8. Which of those a workspace sees is set per workspace: see [Signals and workspaces](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/signals.md).

### Terminology

* **Workspace** — A boundary that controls user and data access. Every organization starts with a **Default**workspace.
* **Source** — An instance of a source type (e.g. CloudWatch). You can add multiple sources of the same type with different credentials (e.g. one per AWS account or region).
* **Stream Type** — The kind of stream produced by a source, e.g. a CloudWatch Lambda log group, a Kubernetes DaemonSet or Deployment, or, for OpenTelemetry sources, a **service**.
* **Stream** — A specific instance of a stream type, e.g. a particular container, pod, or Lambda function.

### Workspaces

A workspace is a boundary that controls who and what can access a given set of data. Common patterns:

* An **environment** — e.g. `staging`, `production`.
* An **application or service** — scoped to the team or developer(s) that own it.
* Any other grouping that fits your organization.

Each workspace has:

* **Its own users** — control exactly who can access its data.
* **Its own streams** — assigned from one or more sources (see Assigning streams to workspaces below).
* **Its own Möbius scope** — the Möbius AI agent operates only against the data in the workspace it's invoked from.

Every organization starts with a **Default** workspace.

### Supported sources

* **Amazon ECS** — Send ECS service logs through the CloudWatch or OpenTelemetry sources
* **AWS CloudWatch** — Stream logs from CloudWatch Log Groups through a Firehose stack you launch in your AWS account
* **Cloudflare** — Receive Cloudflare Logpush jobs over HTTP
* **Docker** — Run the ControlTheory agent on a Docker host to collect container logs
* **GitHub** — Receive webhook events from GitHub
* **Google Cloud** — Pull logs from Google Cloud Logging
* **Kubernetes** — Collect pod logs and events from Kubernetes clusters, and optionally Prometheus metrics
* **OpenTelemetry** — Receive logs, metrics and traces from any OpenTelemetry SDK or collector
* **Railway** — Pull logs from the environments of a Railway project
* **Supabase** — Receive logs from Supabase via OTLP log drain
* **Vercel** — Receive webhook events from Vercel

### Adding a source

1. Go to **Sources** in the sidebar and click **Add Source**.
2. Select a source type.
3. Configure the source (name and any source-specific settings).
4. Provide credentials if required, then click **Test Connection** to verify.
5. Click **Create**.

Some sources need one more step in the upstream platform after you create them: paste the webhook URL into the provider, or, for AWS CloudWatch, launch the setup stack in your AWS account (see [AWS CloudWatch](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/sources/aws-cloudwatch.md)).

New sources start as **Listening for telemetry**. It can take a couple of minutes for data to begin flowing. Once streams are detected, the source turns **Healthy** and its streams are listed with their inferred stream types. See [Signals and workspaces](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/signals.md#which-signals-a-source-sends) for every status and what it means.

### Assigning streams to workspaces

Creating a source ingests its data, but streams must be **assigned to a workspace** before they're accessible there. Each workspace can receive a different subset — for example, production streams to one workspace and staging to another.

1. In the **Sources** list, open the actions menu on a source (gear icon) and select **Assign Streams**.
2. For each workspace, check the streams you want it to receive. Selections are hierarchical — checking a **Stream Type** includes all of its streams, and checking a **Workspace** includes everything from that source.
3. Click **Save Assignments**. For an OpenTelemetry source you can also assign individual services; see [Signals and workspaces](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/signals.md#opentelemetry-sources-assign-by-service).

The number of workspaces currently receiving streams from a source is shown on the source card.

### Source actions

From the actions menu (gear icon) on a source:

* **Edit** — update name and configuration.
* **Assign Streams** — manage which workspaces receive which streams (above).
* **Test Connection** — re-verify credentials (sources that pull with credentials).
* **Disable** — pause ingestion without deleting the source.
* **Delete** — remove the source permanently.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.controltheory.com/controltheory-documentation/dstl8-docs/sources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
