feat(OpenTelemetry): Starting removing pre-release references. Added …

…beta doc material.

src/content/docs/integrations/open-source-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic.mdx

@@ -176,6 +176,8 @@ New Relic supports the native OpenTelemetry Protocol (OTLP) for exporting teleme
 
 Support for OTLP Trace ingest:
 
+[INSERT MORE DETAILS HERE AND AUGUMENT TABLE] 
+
 <table>
   <thread>
     <tr>
@@ -242,6 +244,14 @@ We currently support the ingest of OTLP metrics with delta aggregation temporali
   </tbody>
 </table>
 
+## Logs
+
+We offer experimental support for OTLP Log ingest.
+
+[INSERT DETAILS HERE]
+
+## Next steps
+
 Follow the [OpenTelemetry quick start](/docs/integrations/open-source-telemetry-integrations/opentelemetry/set-opentelemetry-new-relic) to help you get started.
 
 You'll also want to review the [best practices](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts) guide for getting the most out of the data you export to New Relic.

src/content/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts.mdx

@@ -24,7 +24,7 @@ Make sure you are familiar with the options for sampling trace spans.
 
 ### Sampling [#sampling]
 
- Trace data is the most mature OpenTelemetry data type. Because of this, New Relic's OpenTelemetry user experience is largely based on trace data and is therefore influenced by your sampling strategy.
+Trace data is the most mature OpenTelemetry data type. Because of this, New Relic's OpenTelemetry user experience is largely based on trace data and is therefore influenced by your sampling strategy.
 
 You can configure sampling in a number of places:
 

src/content/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-quick-start.mdx

@@ -48,10 +48,6 @@ Go to the repository for your language and follow the instructions to instrument
 
 The [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md), or OTLP for short, is a general purpose telemetry data delivery protocol designed for the OpenTelemetry project. This protocol describes how to encode and transmit telemetry data, which makes it a natural choice for data transport. Each language SDK provides an OTLP exporter you can configure to export data over OTLP. 
 
-<Callout variant="important">
-Our support of OTLP ingest is currently in pre-release. To participate in the pre-release program, please complete this [form](https://docs.google.com/forms/d/e/1FAIpQLSdIJVEAYaP7TXe9LmQA64yIObGvt-nOiz5kXYsjxLBbvut_1A/viewform), and we'll send you details.
-</Callout>
-
 In this step, we focus on how to configure an OTLP exporter in your service to export data directly to New Relic:
 
 ![Diagram showing OpenTelemetry using New Relic's OTLP endpoint.](./images/native_otlp.svg "Diagram of OTLP endpoint")
@@ -60,10 +56,58 @@ In this step, we focus on how to configure an OTLP exporter in your service to e
 If you prefer to export your data to an OpenTelemetry collector, see our [instructions](#collector) below.
 </Callout>
 
-To complete this step, you'll follow the OTLP exporter documenentation for your language. Before you go to this external documentation, keep in mind you'll need to configure the OTLP exporter to send data to New Relic. This includes setting the header and configuring the endpoint:
+To complete this step, you'll follow the OTLP exporter documenentation for your language. Before you go to this external documentation, keep in mind you'll need to configure the OTLP exporter to send data to New Relic: 
 
 * Configure the OTLP exporter to add a header ( ```api-key``` ) whose value is your [Account License Key](https://one.newrelic.com/launcher/api-keys-ui.launcher).
-* Configure the endpoint for the exporter to point to New Relic. You'll receive the endpoint URL when you sign up for the [pre-release program](https://docs.google.com/forms/d/e/1FAIpQLSdIJVEAYaP7TXe9LmQA64yIObGvt-nOiz5kXYsjxLBbvut_1A/viewform). 
+* Configure the endpoint for the exporter to point to New Relic.  
+
+<table>
+  <thead>
+    <tr>
+      <th>Region</th>
+      <th>gRPC</th>
+      <th>HTTP</th>
+      <th>Endpoint</th>
+      <th>API Header Name</th>
+      <th>API Header Value</th>
+      <th>TLS encryption required</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>US</td>
+      <td>✅</td>
+      <td>❌</td>
+      <td><a href="https://otlp.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://otlp.nr-data.net:4317</a></td>
+      <td><code>api-key</code></td>
+      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
+      <td>✅</td>
+    </tr>
+    <tr>
+      <td>EU</td>
+      <td>✅</td>
+      <td>❌</td>
+      <td><a href="https://otlp.eu01.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://otlp.eu01.nr-data.net:4317</a></td>
+      <td><code>api-key</code></td>
+      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
+      <td>✅</td>
+    </tr>
+        <tr>
+      <td>FedRamp</td>
+      <td>✅</td>
+      <td>❌</td>
+      <td><a href="https://gov-otlp.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://gov-otlp.nr-data.net:4317</a></td>
+      <td><code>api-key</code></td>
+      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
+      <td>✅</td>
+    </tr>
+  </tbody>
+</table>
+
+<Callout variant="important">
+In NodeJS, the [opentelemetry-collector-grpc](https://www.npmjs.com/package/@opentelemetry/exporter-collector-grpc) library requires additional options to enable TLS.
+</Callout>
+
 
 Now, follow the instructions for your language: