> 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/integrations/destinations/dev-null.md).

# Dev Null

Dev Null discards every record sent to it. It exports metrics, logs, and traces using the OpenTelemetry Collector's built-in `nop` exporter, which accepts data and drops it. Use it as a placeholder when you want a valid pipeline without a real destination, or to measure source and processor throughput in isolation.

### Supported Telemetry

| Metrics | Logs | Traces |
| ------- | ---- | ------ |
| ✓       | ✓    | ✓      |

### Prerequisites

None. Dev Null requires no account, credentials, endpoint, or network access. It runs entirely inside the collector.

### Configuration

<figure><img src="/files/RgH5s3SYulRkJ2JlpQ2x" alt="Bindplane docs - Dev Null - image 1"><figcaption></figcaption></figure>

**Basic**

| Parameter             | Type               | Required | Default               | Description                                                                                               |
| --------------------- | ------------------ | -------- | --------------------- | --------------------------------------------------------------------------------------------------------- |
| Choose Telemetry Type | Telemetry Selector | No       | Logs, Metrics, Traces | Which signals this destination discards. Any selected signal is routed to the `nop` exporter and dropped. |

**Advanced**

| Parameter     | Type    | Required | Default | Description                                                                                                                 |
| ------------- | ------- | -------- | ------- | --------------------------------------------------------------------------------------------------------------------------- |
| Drop Raw Copy | Boolean | No       | `true`  | When enabled, the raw copy of the log stored in `log.record.original` is dropped before the record is discarded. Logs only. |

### Examples

Discard all telemetry to test how much throughput a set of sources and processors can sustain without a backend in the path.

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: dev-null
spec:
  type: dev_null
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
```

### Configuration Tips

* Use Dev Null to keep a pipeline valid while a real destination is being provisioned, then swap it out without rebuilding the pipeline.
* Narrow Choose Telemetry Type to a single signal when you only want to drop one signal and route the others to a real destination.

### Troubleshooting

#### Data still reaches a backend

Symptoms: telemetry shows up downstream even though Dev Null is attached.

Solution: confirm the pipeline routes the signal to the Dev Null destination and not to another destination in parallel. Dev Null only discards the signals routed to it.

#### A signal is not being dropped

Symptoms: one signal still flows through while others are discarded.

Solution: check Choose Telemetry Type. A signal that is not selected is not handled by this destination.

### Standalone Destination

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: dev-null
spec:
  type: dev_null
  parameters:
    - name: telemetry_types
      value:
        - Logs
        - Metrics
        - Traces
```

### Related Resources

* [nopexporter — OpenTelemetry Collector exporter reference](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/nopexporter)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.bindplane.com/integrations/destinations/dev-null.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.