Merge pull request #4041 from newrelic/Add-otlp-to-networks

fix(Networks): added OTLP per issue 4038

src/content/docs/using-new-relic/cross-product-functions/install-configure/networks.mdx

@@ -152,6 +152,15 @@ If your organization uses a firewall that restricts outbound traffic, ensure tha
         Support for reCAPTCHA
       </td>
     </tr>
+
+    <tr>
+      <td>
+        *.nr-data.net
+      </td>
+      <td>
+        OpenTelemetry and Pixie
+      </td>
+    </tr>
   </tbody>
 </table>
 
@@ -452,4 +461,14 @@ 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)
+* otlp.eu01.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.
+
+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. See the [OpenTelemetry quick start](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-quick-start/) for more information.
+
+* otlp.nr-data.net:4317 (US region accounts)
+* otlp.eu01.nr-data.net:4317 (EU region accounts)