> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# New Relic Logs destination plugin

> Configure the New Relic Logs destination plugin in Palo Alto Networks Telemetry Pipeline to send logs to New Relic.

export const entity_0 = "New Relic Logs destination plugin"

export const plugin_0 = "New Relic Logs destination plugin"

<Info>
  This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
  product separate from Palo Alto Networks Cortex XCOR.
</Info>

The New Relic Logs [destination plugin](/ingest/pipeline/plugins/destination-plugins)
(name: `nrlogs`) lets you configure your telemetry pipeline to send your log
data to New Relic Logs.

## Supported telemetry types

The {plugin_0} for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

| Logs | Metrics | Traces |
| :-: | :-: | :-: |
| <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Palo Alto Networks Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-files)
use the items in the **Key** column as YAML keys.

### Required

| Name | Key | Description | Default |
| - | - | - | - |
| **New Relic API Key** | `api_key` | Required. Your key for data ingestion. The API key is also called the ingestion key. For more details about how to generate the API key, see the [official documentation](https://docs.newrelic.com/docs/apis/get-started/intro-apis/types-new-relic-api-keys#event-insert-key). From a configuration perspective, either an `api_key` or an `license_key` is required. New Relic suggests using `api_key`. | *none* |

### Advanced

| Name | Key | Description | Default |
| - | - | - | - |
| **New Relic License Key** | `license_key` | Optional authentication parameter for data ingestion. New Relic suggests you instead use the `api_key`. [License Key information](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/license-key). | *none* |
| **Compression** | `compress` | Compression type for the payload. | `gzip` |
| **New Relic Base URI** | `base_uri` | Full address of New Relic API endpoint. For the EU endpoint, set this key to `https://log-api.eu.newrelic.com/log/v1`. | `https://log-api.newrelic.com/log/v1` |

### Security and TLS

| Name | Key | Description | Default |
| - | - | - | - |
| **TLS** | `tls` | If `true`, enables TLS/SSL. If `false`, disables TLS/SSL. Accepted values: `true`, `false`. | `false` |
| **TLS Certificate Validation** | `tls.verify` | If `on`, and if `tls` is `true`, enables TLS/SSL certificate validation. If `off`, disables TLS/SSL certificate validation. Accepted values: `on`, `off`. | `on` |
| **TLS Debug Level** | `tls.debug` | Sets TLS debug verbosity level. Accepted values: `0` (No debug), `1` (Error), `2` (State change), `3` (Informational), `4` (Verbose). | `1` |
| **CA Certificate File Path** | `tls.ca_file` | Absolute path to CA certificate file. | *none* |
| **Certificate File Path** | `tls.crt_file` | Absolute path to certificate file. | *none* |
| **Private Key File Path** | `tls.key_file` | Absolute path to private key file. | *none* |
| **Private Key Path Password** | `tls.key_passwd` | Password for private key file. | *none* |
| **TLS SNI Hostname Extension** | `tls.vhost` | Hostname to be used for TLS SNI extension. | *none* |

### Advanced Networking

| Name | Key | Description | Default |
| - | - | - | - |
| **DNS Mode** | `net.dns.mode` | Selects the primary DNS connection type, which can be `TCP` or `UDP`. | *none* |
| **DNS Resolver** | `net.dns.resolver` | Selects the primary DNS connection type, which can be `LEGACY` or `ASYNC`. | *none* |
| **Prefer IPv4** | `net.dns.prefer_ipv4` | Prioritizes IPv4 DNS results when trying to establish a connection. Accepted values: `true`, `false`. | `false` |
| **Keepalive** | `net.keepalive` | Enables or disables Keepalive support. Accepted values: `true`, `false`. | `true` |
| **Keepalive Idle Timeout** | `net.keepalive_idle_timeout` | Sets the maximum time allowed for an idle Keepalive connection. | `30s` |
| **Max Connect Timeout** | `net.connect_timeout` | Sets the maximum time allowed to establish a connection, which includes the TLS handshake. | `10s` |
| **Max Connect Timeout Log Error** | `net.connect_timeout_log_error` | Specifies whether to log an error on connection timeout. When disabled, the timeout is logged as a debug message. Accepted values: `true`, `false`. | `true` |
| **Source Address** | `net.source_address` | Specifies the network address to bind for data traffic. | *none* |
| **Max Keepalive Recycle** | `net.keepalive_max_recycle` | Sets the maximum number of times a keepalive connection can be used before it's retired. | `2000` |


## Related topics

- [Datadog Logs destination plugin](/ingest/pipeline/plugins/destination-plugins/datadog.md)
- [Dynatrace Logs destination plugin](/ingest/pipeline/plugins/destination-plugins/dynatrace.md)
- [Oracle Log Analytics destination plugin](/ingest/pipeline/plugins/destination-plugins/oracle.md)
- [Azure Monitor Logs destination plugin](/ingest/pipeline/plugins/destination-plugins/azure-monitor.md)
- [Cortex XCOR Logs destination plugin](/ingest/pipeline/plugins/destination-plugins/chronosphere.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.