Edge Delta New Relic Destination

Overview

The New Relic destination node sends items to a New Relic destination.

• incoming_data_types: cluster_pattern_and_sample, log, metric, custom

This node requires Edge Delta agent version v0.1.99 or higher.

Example Configuration

nodes:
  - name: my_newrelic
    type: newrelic_output
    api_key: <REDACTED>

Required Parameters

name

A descriptive name for the node. This is the name that will appear in pipeline builder and you can reference this node in the YAML using the name. It must be unique across all nodes. It is a YAML list element so it begins with a - and a space followed by the string. It is a required parameter for all nodes.

nodes:
  - name: <node name>
    type: <node type>

type: newrelic_output

The type parameter specifies the type of node being configured. It is specified as a string from a closed list of node types. It is a required parameter.

nodes:
  - name: <node name>
    type: <node type>

api_key

The api_key parameter specifies the ingest key provided by New Relic to send data to your New Relic account. It is required.

nodes:
 - name: my_newrelic
   type: newrelic_output
   api_key: <REDACTED>

Optional Parameters

log_endpoint

The log_endpoint parameter specifies where logs will be sent. The default value is https://log-api.newrelic.com/log/v1.

nodes:
  - name: my_newrelic
    type: newrelic_output
    log_endpoint: "https://log-api.newrelic.com/log/v1"

metric_endpoint

The metric_endpoint parameter specifies where metrics will be sent. The default value is https://metric-api.newrelic.com/metric/v1.

nodes:
  - name: my_newrelic
    type: newrelic_output
    metric_endpoint: "https://metric-api.newrelic.com/metric/v1"

buffer_max_bytesize

The buffer_max_bytesize parameter configures the maximum byte size for total unsuccessful items. If the limit is reached, the remaining items are discarded until the buffer space becomes available. It is specified as a datasize.Size, has a default of 0 indicating no size limit, and it is optional.

nodes:
  - name: <destination-name>
    type: <destination-type>
    buffer_max_bytesize: 2048

buffer_path

The buffer_path parameter configures the path to store unsuccessful items. Unsuccessful items are stored there to be retried back (exactly once delivery). It is specified as a string and it is optional.

Note: Buffered data may be delivered in non-chronological order after a destination failure. Event ordering is not guaranteed during recovery. Applications requiring ordered event processing should handle reordering at the application level.

nodes:
  - name: <destination-name>
    type: <destination-type>
    buffer_path: <path to unsuccessful items folder>

buffer_ttl

The buffer_ttl parameter configures the time-to-Live for unsuccessful items, which indicates when to discard them. It is specified as a duration, has a default of 10m, and it is optional.

nodes:
  - name: <destination-name>
    type: <destination-type>
    buffer_ttl: 20m