Update New Relic references to refer to OTLP instead of deprecated exporter (#177)

* Adding New Relic native OTLP support

* Update New Relic partner link for otlp

* Remove deprecated New Relic exporter page

Author: jsgithub1

src/config/sideBarData.js

@@ -113,7 +113,7 @@ export const sideBarData = [
         {label: "Honeycomb", link: "/docs/components/otlp-exporter#honeycomb"},
         {label: "Lightstep", link: "/docs/components/otlp-exporter#lightstep"},
         {label: "Logz.io", link: "/docs/partners/logzio"},
-        {label: "New Relic", link: "/docs/partners/new-relic"},
+        {label: "New Relic", link: "/docs/components/otlp-exporter#new-relic"},
         {label: "Splunk", link: "/docs/partners/splunk"},
         {label: "Sumo Logic", link: "/docs/components/otlp-exporter#sumo-logic"},
       ],

src/docs/components/otlp-exporter.mdx

@@ -51,7 +51,7 @@ and expects to receive a response with each request. You can learn more about th
 OpenTelemetry can export traces, logs, and metrics to various backends to analyze in order to understand an application’s performance
 and behavior. There are multiple monitoring backends (also known as end-points) which can support OpenTelemetry using the OTLP protocol.
 
-In this section, we share getting started configurations to the Collector to export telemetry data to **AppDynamics, Honeycomb, Lightstep, and SumoLogic** end-points.
+In this section, we share getting started configurations to the Collector to export telemetry data to **AppDynamics, Honeycomb, Lightstep, New Relic, and SumoLogic** end-points.
 
 <SectionSeparator />
 
@@ -383,6 +383,45 @@ exporters:
 
 <SectionSeparator />
 
+## New Relic
+
+New Relic supports OpenTelemetry natively, via OTLP.  If you’re already set up with the AWS Distro for OpenTelemetry, then
+sending data to New Relic can be accomplished with a simple change to the collector's YAML config file.
+
+<SubSectionSeparator />
+
+### Requirements
+
+Before you can use the AWS Distro for OpenTelemetry with New Relic, you will need:
+
+* A New Relic account. If you don't already have one, you can [sign up for a free account](https://newrelic.com/signup).
+* An [Ingest-License Key](https://one.newrelic.com/launcher/api-keys-ui.launcher) for your account.  Select "Create a Key" and "Ingest-License Key" for the type.
+
+<SubSectionSeparator />
+
+### Configuration (Collector)
+
+The configuration will take place in the OTLP exporter section of the Collector config YAML file.
+
+* Set the OTLP endpoint to [otlp.nr-data.net:4317](https://otlp.nr-data.net:4317/)
+* Add your New Relic Ingest-License key as an OTLP header.
+    * Header name: "api-key"
+
+<SubSectionSeparator />
+
+### Example
+
+```yaml lineNumbers=true highlight={8}
+# New Relic OTLP Collector configuration
+exporters:
+  otlp:
+    endpoint: otlp.nr-data.net:4317
+    headers: 
+      api-key: <YOUR_NEW_RELIC_LICENSE_KEY>
+```
+
+<SectionSeparator />
+
 ## OpenSearch
 OpenSearch supports ingesting enchriched trace data via [Data Prepper](https://github.com/opensearch-project/data-prepper), a standalone application that converts OLTP formatted data for use in OpenSearch. Data Prepper supports receiving trace data from OpenTelemetry natively via OTLP. Once you've set up a Data Prepper instance, completing the data pipeline is as simple as editing your YAML config file for the Collector and getting started.