> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data plane settings

> Choose how the service map is built, link clusters for federated queries, and cancel queries that run too long.

These sections of **Settings** act on the data plane of the workspace: **Nodes / remote clusters**
under **Data plane**, and **Query management** under **AI & ML**. Reading them requires
`org.settings.read`, and changing them requires `org.settings.manage`. The data plane settings of
the whole instance, such as the default retention, are [platform settings](https://docs.molesignal.com/en-US/settings/platform.md).

## Nodes and remote clusters

Open **Settings → Nodes / remote clusters**.

### Service data source

**Recompute from storage (multi-node)** decides how the [service map](https://docs.molesignal.com/en-US/apm/service-map.md) is
built from traces:

| Setting | How | Trade-off |
| - | - | - |
| On | One node rebuilds the service map from the stored traces at intervals. | Correct across nodes, about 1 to 2 minutes behind. |
| Off | Every intake process pairs spans in memory and flushes the result. | Low delay, but calls whose spans arrive at different intake nodes can be undercounted. |

Turn it on for a deployment with several intake nodes.

### Cluster federation

Federation keeps resource changes in step between clusters. Enter a **Cluster ID** that is unique in
the federation and stays the same across restarts, for example `cluster-eu-west`, and select
**Save changes**. An empty cluster ID turns federation off, after a confirmation. Local data is not
affected when federation stops.

**Advanced parameters** tune the exchange: **Outbox push interval (s)**, **Push batch size**,
**Dedup window (s)**, and **Gossip interval (s)**.

### Remote clusters

A remote cluster is a target of [federated queries](https://docs.molesignal.com/en-US/deployment/role-based.md#federated-query).

1. Select **Add cluster**.
2. Enter a **Name** and the **Advertise address** of the remote cluster, for example
   `https://cluster.example.com`.
3. Enter the **Token secret ref**: a reference such as `env:VAR` or `cipher_keys:<id>`, never the token
   itself. The list shows it as `***`.
4. Keep **Verify TLS certificate** on unless the remote cluster uses a private certificate that this
   cluster cannot verify.
5. Select **Add cluster**.

Each row has two more actions:

| Action | Shows |
| - | - |
| **Nodes** | The nodes of the remote cluster, with their roles and versions, or an error when it cannot be reached. |
| **Org map** | The mappings of remote organizations to local ones. Configuration from an unmapped organization is refused. A mapping can carry its own **Per-org token ref**, otherwise the cluster token applies. |

Removing a cluster stops federated queries from reaching it.

## Query management

**Settings → Query management** lists the queries of the workspace that run now, with the query ID,
the user, the start time, and the statement. The list refreshes every 3 seconds. **Cancel** stops a
query. Search jobs that run in the background are managed under
[Streams → Search jobs](https://docs.molesignal.com/en-US/streams.md#search-jobs) instead.

| Operation | Endpoint | Permission |
| - | - | - |
| List running queries | `GET /api/v1/query/running` | `org.settings.read` |
| Cancel a query | `POST /api/v1/query/{id}/cancel` | `org.settings.manage` |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.