---
title: Datadog BYOC Logs Destination
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Observability Pipelines > Destinations > Datadog BYOC Logs Destination
---

# Datadog BYOC Logs Destination

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ().
{% /alert %}

{% /callout %}
Available for:
{% icon name="icon-logs" /%}
 Logs 
## Overview{% #overview %}

Use Observability Pipelines' Bring Your Own Cloud (BYOC) Logs destination to send logs to Datadog BYOC Logs.

## Prerequisites{% #prerequisites %}

Before configuring the destination, you need to deploy a BYOC Logs cluster. Learn how to install it in the [BYOC Logs installation section](https://docs.datadoghq.com/byoc-logs/install.md).

## Setup{% #setup %}

Configure the BYOC Logs destination when you [set up a pipeline](https://docs.datadoghq.com/observability_pipelines/configuration/set_up_pipelines.md). You can set up a pipeline in the [UI](https://app.datadoghq.com/observability-pipelines), using the [API](https://docs.datadoghq.com/api/latest/observability-pipelines.md), or with [Terraform](https://registry.terraform.io/providers/datadog/datadog/latest/docs/resources/observability_pipeline). The steps in this section are configured in the UI.

### Optional buffering{% #optional-buffering %}

After you select the BYOC Logs destination in the pipeline UI, you can configure buffering.

Toggle the switch to enable **Buffering Options**. Enable a configurable buffer on your destination to ensure intermittent latency or an outage at the destination doesn't create immediate backpressure, and allow events to continue to be ingested from your source. Disk buffers can also increase pipeline durability by writing data to disk, ensuring buffered data persists through a Worker restart. See [Destination buffers](https://docs.datadoghq.com/observability_pipelines/scaling_and_performance/buffering_and_backpressure.md#destination-buffers) for more information.

- If left unconfigured, your destination uses a memory buffer with a capacity of 500 events.
- To configure a buffer on your destination:
  1. Select the buffer type you want to set (**Memory** or **Disk**).
  1. Enter the buffer size and select the unit.
     1. Maximum memory buffer size is 128 GB.
     1. Maximum disk buffer size is 500 GB.
  1. In the **Behavior on full buffer** dropdown menu, select whether you want to **block** events or **drop new events** when the buffer is full.

{% image
   source="https://docs.dd-static.net/images/observability_pipelines/destinations/cloudprem_settings.3e66f2b97b3eacdd3ad1ed315dbb83ff.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/observability_pipelines/destinations/cloudprem_settings.3e66f2b97b3eacdd3ad1ed315dbb83ff.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The BYOC Logs destination settings" /%}

## Secret defaults{% #secret-defaults %}

These are the defaults used for secret identifiers and environment variables.

**Note**: If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with `DD_OP`. For example, if you entered `PASSWORD_1` for a password identifier, the environment variable for that password is `DD_OP_PASSWORD_1`.

{% tab title="Secrets Management" %}

- BYOC Logs endpoint URL identifier:
  - References the intake endpoint to which Observability Pipelines sends logs.
  - In your secrets manager:
    - Define the cluster URL, such as `http://cloudprem.acme.internal:7280`. **Note**: The URL must include the port.
    - The Worker appends `/api/v2/logs` and `/api/v1/validate` to the endpoint URL, so these endpoints must be allowed if you are using forwarding or firewall rules.
  - The default identifier is `DESTINATION_CLOUDPREM_ENDPOINT_URL`.

{% /tab %}

{% tab title="Environment Variables" %}

{% image
   source="https://docs.dd-static.net/images/observability_pipelines/destinations/cloudprem_env_vars.0c7413960b2d4918ffdb5f6caf4e0f50.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/observability_pipelines/destinations/cloudprem_env_vars.0c7413960b2d4918ffdb5f6caf4e0f50.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The install page showing the BYOC Logs environment variable field" /%}

- BYOC Logs endpoint URL
  - Observability Pipelines sends logs to the BYOC Logs intake endpoint. Define the cluster URL, such as `http://cloudprem.acme.internal:7280`. **Note**: The URL must include the port.
  - The Worker appends `/api/v2/logs` and `/api/v1/validate` to the endpoint URL, so these endpoints must be allowed if you are using forwarding or firewall rules.
  - Stored as the environment variable: `DD_OP_DESTINATION_CLOUDPREM_ENDPOINT_URL`.

{% /tab %}

## How the destination works{% #how-the-destination-works %}

### Event batching{% #event-batching %}

A batch of events is flushed when one of these parameters is met. See [event batching](https://docs.datadoghq.com/observability_pipelines/destinations.md#event-batching) for more information.

| Maximum Events | Maximum Size (MB) | Timeout (seconds) |
| -------------- | ----------------- | ----------------- |
| 1,000          | 4.25              | 5                 |