fix(Networks): added OTLP per issue 4038

newrelic · Sep 23, 2021 · 3b7d528 · 3b7d528
1 parent 2f81779
commit 3b7d528
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/...ent/docs/using-new-relic/cross-product-functions/install-configure/networks.mdx b/...ent/docs/using-new-relic/cross-product-functions/install-configure/networks.mdx
@@ -453,3 +453,13 @@ The Pixie integration requires outbound network access to the following:
 * work.withpixie.ai:443
 * otlp.nr-data.net:4317 (US region accounts)
 * eu.otlp.nr-data.net:4317 (EU region accounts)
+
+## OpenTelemetry 
+
+New Relic supports the native OpenTelemetry Protocol (OTLP) for exporting telemetry data. This allows you to use the vendor neutral components developed by the OpenTelemetry community to export your data to New Relic. See our [OpenTelemetry docs](/docs/integrations/open-source-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic/#how-it-works) for more information.
+
+To export OTLP data to New Relic, configure the OTLP exporter to add a header ( api-key ) whose value is your account license key.
+And, based on your region, configure the endpoint where the exporter sends data to New Relic.
+
+* otlp.nr-data.net:4317 (US region accounts)
+* eu.otlp.nr-data.net:4317 (EU region accounts)