# Pausing Telemetry

By default, telemetry is collected from all sources in a configuration and sent to all supported destinations in that configuration. However, there may be times when you don't want to collect from a particular source or export to a destination. To support those situations, Bindplane allows you to "Pause" sources and destinations. When a source is paused, collectors won't try to collect from it. When a destination is paused, no collected telemetry will be sent to it.

An important detail to remember is that pausing or resuming a source or destination in a configuration will update all collectors using that configuration to pause/resume that source/destination.

## Pausing a Source

Sources can be paused from the page of either a collector or its configuration. To pause a source, click on the card for the source you want to pause in the topology view. The current status will be displayed in the bottom left corner, indicating whether it is `Running` or `Paused`. If running, clicking the `Pause` button will pause collection of that source.

<figure><img src="/files/emkOXPqE9GE1bxzxCgd6" alt="Bindplane docs - Pausing Telemetry - image 1"><figcaption></figcaption></figure>

After clicking "Pause", the topology reflects that the Active Directory source has been paused.

<figure><img src="/files/PLn0IgX6AdzxpvQsJ0bE" alt="Bindplane docs - Pausing Telemetry - image 2"><figcaption></figcaption></figure>

### Pausing a Destination

Destinations can be paused like sources, by clicking on the appropriate card in the topology view of a configuration. Its current status will be shown in the bottom left corner, either `Running` or `Paused`. If running, clicking the `Pause` button will pause the sending of telemetry to that destination. If the only destination in a configuration is paused, the collector will also pause collecting all sources as the telemetry has nowhere to go.

A major difference between pausing sources and destinations is that while pausing a source only affects that configuration, pausing a destination will pause it in all configurations including it. For example, imagine a single Google Cloud Monitoring destination, `example-gcp-project`, is being used in several configurations to send telemetry to that GCP project. If you need to stop all telemetry from being sent, pausing the `example-gcp-project` destination in one configuration will pause it in all other configurations.

<figure><img src="/files/KVmVOU0JhEZQQ6YZvmyU" alt="Bindplane docs - Pausing Telemetry - image 3"><figcaption></figcaption></figure>

After clicking "Pause", the topology reflects that the `Gcloud-qa` destination has been paused.

<figure><img src="/files/pLTsHYcaROpIPRAmLFoo" alt="Bindplane docs - Pausing Telemetry - image 4"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/feature-guides/data-management/pausing-telemetry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
