> 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/signals.md).

# Signals and Workspaces

Logs, metrics and traces in a workspace, choosing which ones each workspace gets, and reading them side by side

A workspace is a boundary around a set of data, with its own users and the streams you assign to it from your sources (see [Workspaces](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/sources.md#workspaces)). Dstl8 works with three signals: **logs**, **metrics** and **traces**. A source can send one, two or all three, and each workspace decides which of them it gets from each source. Once they arrive, the workspace dashboard and every service page draw them as lanes on one shared timeline, so you can see in one glance whether an error burst in the logs lines up with failing requests or a metric change.

Events and sentiment are views over these signals: [Events](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/events.md) are the changes and Kubernetes events recorded alongside your telemetry, and the **Sentiment** page scores your logs.

## Which signals a source sends

On **Sources** (under Organization Settings in the sidebar), each source and each of its streams carries small tags naming the signals it sends, such as `METRICS` or `TRACES`. A source or stream that sends only logs has no tag, since logs are the usual case.

The status beside each source tells you whether data is arriving:

| Status                      | Meaning                                                                                                                            |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Healthy**                 | Streams detected; telemetry is flowing normally.                                                                                   |
| **Listening for telemetry** | The source is enabled but no logs, metrics or traces have arrived yet. New sources start here.                                     |
| **Degraded**                | The source is not running.                                                                                                         |
| **Missing credentials**     | A stored secret for this source could not be retrieved and may have been deleted. Edit the source and enter the credentials again. |
| **Disabled**                | The source is turned off and not collecting data.                                                                                  |

From the CLI, `dstl8 sources streams <source>` lists a source's streams with a **SIGNALS** column.

## Getting signals into a workspace

A workspace sees only the streams assigned to it. To assign them:

1. Go to **Sources**, open the gear menu on a source and choose **Assign Streams**.
2. In **Manage Stream Assignments**, check a workspace to give it every stream of the source, or open it and pick streams one by one. Turn on **All streams (includes new streams)** to also include streams the source starts sending later.
3. Click **Save Assignments**.

You can also start from the workspace: on **Workspaces**, open a workspace card's gear menu and choose **Assign Streams**.

### OpenTelemetry sources: assign by service

An OpenTelemetry source lists a **service** stream for each `service.name` it receives, tagged with the signals that service sends. Assigning a service stream gives the workspace that service's logs, metrics and traces together, from every instance of it. This is how you put one service's telemetry in a team's workspace without the rest of the source.

Metrics and traces that carry no `service.name` have no stream to pick. The dialog says so ("Sends metrics and traces without a service name: only All streams scopes them"); to give a workspace that data, turn on **All streams** for the source. Better still, set `service.name` in your SDK or collector. See [OpenTelemetry (OTel)](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/sources/opentelemetry-otel.md).

## Choosing signals per workspace

When a source sends more than one signal, each workspace can take only some of them. For example, a production workspace can take a source's logs, metrics and traces while a performance workspace takes only its traces.

1. Open **Assign Streams** on the source, from the **Sources** page.
2. Expand the workspace. Under **Signals this workspace gets**, check **Logs**, **Metrics** and **Traces** as you want them.
3. Click **Save Assignments**.

What the boxes do:

* **At least one stays checked.** To take nothing from the source, uncheck the workspace itself.
* **Unchecking a signal** keeps that kind of data from the source out of the workspace's views and out of what Möbius sees there.
* **With every box checked**, the workspace also gets any kind of data the source starts sending later. If a source sends only logs today and you add tracing next month, the traces arrive in the workspace without another visit to this dialog. With a narrower choice, a new signal stays out until you check it.
* **A narrower choice shows as a badge** on the workspace's row in the dialog, such as **Traces only** or **Logs and Metrics**.

The choice appears only for a source that sends more than one signal, and only once the workspace takes something from it.

## Signal lanes

The workspace dashboard's **Signals (1h)** card, each workspace card on the **Workspaces** page, and the **Signals** card on every [service page](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/services.md#signals) draw the signals as thin lanes on one time axis:

| Lane        | Draws                                                                            | Note beside it                               |
| ----------- | -------------------------------------------------------------------------------- | -------------------------------------------- |
| **Logs**    | Log volume by severity                                                           | Lines per minute and the error share         |
| **Traces**  | Requests per interval, with failed requests in red and the p95 latency as a line | Requests per minute, error share, latest p95 |
| **Metrics** | Datapoints per interval                                                          | Active series and points per minute          |

A signal with nothing in the window has no lane. Hover a lane for the numbers in that interval. When an anomaly began in an interval, the lane marks it and the tooltip says so with its peak. The newest interval or two may show as **Still processing** while the latest data is being read; they fill in shortly.

Under the lanes, one line gives the workspace's leading open metric or trace finding, such as a disk heading for full or a call that started failing. When the finding is on a service, click it to open that service's page. **Nothing unusual in metrics or traces** means the workspace has metrics or traces and nothing is open on them. If the finding could not be read, the line is left out rather than showing an all-clear.

On a workspace card with no data at all, the lanes read **No telemetry**.

## Telling Dstl8 whether a finding was useful

Rows in **Needs attention** on the [Metrics page](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/metrics/explore.md) and in the anomalies on the [Traces page](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/traces/explore.md) have a thumbs-up (**Worth flagging**) and a thumbs-down (**Not worth flagging**). Your vote is recorded with the finding as it stood when you voted and helps us tune what Dstl8 flags. It does not hide or change the row. Click the same thumb again to withdraw the vote. A vote applies to that occurrence of the finding: if the same metric is flagged again later, the new finding starts without a vote.

## Tips

* **Keep traces out of a busy workspace** without touching the source: uncheck **Traces** for that workspace. The other workspaces still get them.
* **One service, its own workspace.** On an OpenTelemetry source, assign just that service's stream to the workspace; it gets all three signals for that service.
* **Seeing logs but not metrics or traces in a workspace?** Check three things: the source's tags show it sends them; the workspace's **Signals this workspace gets** includes them; and the telemetry carries a `service.name` (or the workspace has **All streams**).
* **Lanes look empty for a minute after you assign streams?** New data appears as it arrives; the lanes cover the last hour, so give a new source a few minutes.


---

# 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/signals.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.
