feat(OTEL): Added initial logging support details.

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

@@ -266,7 +266,29 @@ Here are the OpenTelemetry data types we support and their associated mappings.
 
 New Relic offers support for the OTLP ingest of log signals. Note that the maturity of the upstream specification is [experimental](https://github.com/open-telemetry/opentelemetry-specification/blob/87a5ed7f0d4c403e2b336f275ce3e7fd66a8041b/specification/versioning-and-stability.md#experimental). We intend to follow potentially breaking upstream changes.
 
-[INSERT DETAILS HERE]
+OpenTelemetry logs are compatible with New Relic logs. OpenTelemetry logs optionally include attributes (name-value pairs) and resource attributes which map directly to dimensions that can be used to facet or filter log data at query time. OpenTelemetry log metadata (for example, `name`, `severity_text`, and `trace_id`) also map directly to dimensions on New Relic logs. NewRelic currently supports all OpenTelemetry log message types except for arrays.
+
+<table>
+  <thead>
+    <tr>
+      <th style={{ width: "200px" }}>Feature</th>
+      <th>Supported</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Array messages</td>
+      <td>❌</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>Array attributes</td>
+      <td>❌</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
 
 ## Next steps