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

# Sending Queue

A sending queue is a buffer that stores telemetry data temporarily before sending it to the destination. The sending queue ensures that telemetry data is not lost due to network connectivity issues or server outages and helps to minimize the number of network connections required for efficient transmission.

Under the hood, the sending queue is the OpenTelemetry exporter helper's `sending_queue`. For the full queuing behavior, see the [OpenTelemetry exporterhelper documentation](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md).

## Configuration

Destinations show these fields under **Enable Sending Queue**.

<table><thead><tr><th width="271.6953125">Field</th><th width="108.7421875">Type</th><th width="95.25">Default</th><th>Description</th></tr></thead><tbody><tr><td>Enable Sending Queue</td><td><code>bool</code></td><td><code>true</code></td><td>Enable to buffer telemetry data temporarily before sending.</td></tr><tr><td>Number of Consumers</td><td><code>int</code></td><td>10</td><td>The number of consumers that dequeue batches.</td></tr><tr><td>Queue Size</td><td><code>int</code></td><td>5000</td><td>Maximum number of batches kept in memory before dropping.</td></tr><tr><td>Wait for Result</td><td><code>bool</code></td><td><code>false</code></td><td>Block incoming requests until the destination has processed them. Turns off persistent queuing. Only on some destinations; requires Bindplane collector v1.79.1 or newer.</td></tr><tr><td>Block on Overflow</td><td><code>bool</code></td><td><code>false</code></td><td>When the queue is full, block the request until the queue has space instead of rejecting the data immediately. Only on some destinations; requires Bindplane collector v1.79.1 or newer.</td></tr></tbody></table>

### Wait for Result and Block on Overflow

**Wait for Result** and **Block on Overflow** are available on some destinations. Check the destination's configuration to see whether it offers them.

When **Wait for Result** is enabled, the destination can't use a persistent queue, so the **Enable Persistent Queuing** fields are hidden.

{% hint style="warning" %}
Turn off **Enable Persistent Queuing** before you turn on **Wait for Result**. If persistent queuing is left on, the destination renders an invalid sending queue configuration and the collector rejects it.
{% endhint %}

### Per-Destination Defaults

Some destinations use defaults that differ from the table above, tuned to how that destination sends data. The destination's configuration shows its actual defaults.

## Sending Queue and Persistent Queuing

By default, the sending queue holds batches in memory, and they're lost if the collector restarts. [Persistent queuing](/configuration/bindplane-otel-collector/persistent-queue.md) writes the sending queue to disk instead, so queued data survives a restart. Because the persistent queue is the sending queue on disk, persistent queuing is only available when **Enable Sending Queue** is on.


---

# 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.bindplane.com/configuration/bindplane-otel-collector/sending-queue.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.