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

# New Relic Destination

{% callout %}
# Important note for users on the following Datadog sites: app.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 
Use Observability Pipelines' New Relic destination to send logs to New Relic.

## Setup{% #setup %}

Set up the New Relic destination and its environment variables when you [set up a pipeline](https://app.datadoghq.com/observability-pipelines). The information below is configured in the pipelines UI.

### Set up the destination{% #set-up-the-destination %}

{% alert level="danger" %}
Only enter the identifiers for the account ID and license. Do not enter the actual values.
{% /alert %}

1. Enter the identifier for your account ID. If you leave it blank, the default is used.
1. Enter the identifier for your license. If you leave it blank, the default is used.
1. Select the data center region (**US** or **EU**) of your New Relic account.

#### Optional buffering{% #optional-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.

### Set secrets{% #set-secrets %}

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" %}

- New Relic account ID identifier:
  - The default identifier is `DESTINATION_NEW_RELIC_ACCOUNT_ID`.
- New Relic license identifier:
  - The default identifier is `DESTINATION_NEW_RELIC_LICENSE_KEY`.

{% /tab %}

{% tab title="Environment Variables" %}

- New Relic account ID:
  - The default environment variable is `DD_OP_DESTINATION_NEW_RELIC_ACCOUNT_ID`.
- New Relic license:
  - The default environment variable is `DD_OP_DESTINATION_NEW_RELIC_LICENSE_KEY`.

{% /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) |
| -------------- | ----------------- | ----------------- |
| 100            | 1                 | 1                 |