feat(OpenTelemetry): Added tables showing support for OTLP metrics an…

…d traces
newrelic · Sep 21, 2021 · ef78466 · ef78466
1 parent dd7e3fe
commit ef78466
Showing 1 changed file with 70 additions and 0 deletions.
diff --git a/...e-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic.mdx b/...e-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic.mdx
@@ -172,6 +172,76 @@ New Relic supports the native OpenTelemetry Protocol (OTLP) for exporting teleme
 [New Relic's exporters](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) for OpenTelemetry are now deprecated in favor of exporting data to New Relic using OTLP.
 </Callout>
 
+## Traces
+
+Support for OTLP Trace ingest:
+
+<table>
+  <thread>
+    <tr>
+      <th>Feature</th>
+      <th>Supported</th>
+    </tr>
+  <thread>
+  <tbody>
+    <tr>
+      <td>span events</td>
+      <td>✅</td>
+    </tr>
+    <tr>
+      <td>span links</td>
+      <td>❌</td>
+    </tr>
+    <tr>
+      <td>complex types</td>
+      <td>❌</td>
+    </tr>
+  </tbody>
+</table>
+
+## Metrics
+
+We currently support the ingest of OTLP metrics with delta aggregation temporality (including histograms). Cumulative metrics are  converted to gauges. No support yet for cumulative histograms, exemplars, or complex types.
+
+<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>Traces</th>
+      <th>Metrics</th>
+      <th>Logs</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>
+      <td>🟡</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>
+      <td>🟡</td>
+      <td>✅</td>
+    </tr>
+  </tbody>
+</table>
+
 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.