feat(OTEL): Cleanned up some topics in preparation for initial review

newrelic · Sep 21, 2021 · 6421059 · 6421059
1 parent 906d8f3
commit 6421059
Show file tree

Hide file tree

Showing 3 changed files with 40 additions and 12 deletions.
diff --git a/...e-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic.mdx b/...e-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic.mdx
@@ -172,7 +172,7 @@ 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
+### Traces
 
 Support for OTLP Trace ingest:
 
@@ -201,38 +201,53 @@ Support for OTLP Trace ingest:
   </tbody>
 </table>
 
-## Metrics
+### 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.
+We currently support the ingest of OTLP metrics with delta aggregation temporality (including histograms). 
 
 <table>
   <thead>
     <tr>
       <th style={{ width: "200px" }}>Metric Type</th>
+      <th>Supported</th>
       <th>Description</th>
     </tr>
   </thead>
-    <tbody>
+  <tbody>
     <tr>
       <td>Cumulative</td>
-      <td>[INSERT INFO HERE]</td>
+      <td>✅</td>
+      <td>Cumulative metrics are converted to gauges. [INSERT INFO HERE]</td>
     </tr>
     <tr>
       <td>Guages</td>
+      <td>✅</td>
       <td>[INSERT INFO HERE]</td>
     </tr>
     <tr>
       <td>Histograms</td>
+      <td>✅</td>
       <td>[INSERT INFO HERE]</td>
     </tr>
     <tr>
-      <td>Others?</td>
-      <td>[INSERT INFO HERE]</td>
+      <td>Cumulative histograms</td>
+      <td>❌</td>
+      <td>&nbsp;</td>
     </tr>
-    </tbody>
+    <tr>
+      <td>Exemplars</td>
+      <td>❌</td>
+      <td>&nbsp;</td>
+    </tr>
+    <tr>
+      <td>Complex types</td>
+      <td>❌</td>
+      <td>&nbsp;</td>
+    </tr>
+  </tbody>
 </table>
 
-## Logs
+### Logs
 
 We offer experimental support for OTLP Log ingest.
 

diff --git a/...ons/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts.mdx b/...ons/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts.mdx
@@ -14,9 +14,12 @@ Here are some best practices based on how OpenTelemetry works with New Relic.
 
 A resource in OpenTelemetry represents information about an entity generating telemetry data. All telemetry data sent to New Relic is expected to be associated with a resource so that it can be linked with the appropriate entity in New Relic. The [OpenTelemetry Resource SDK specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md) defines the functionality implemented by all language SDKs for defining a resource.
 
-<Callout variant="important">
-At a minimum, the `service.name` attribute must be present on your resource for data to be associated with an entity in New Relic.
-</Callout>
+The following suites of attributes defined by the [OpenTelemtry resource semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource/semantic_conventions#resource-semantic-conventions). These attributes are usually set by creating a resource using the OpenTelemetry SDK.
+
+  * `service.* attributes`
+    * `service.name` attribute is required to associate your resource with an entity in the UI
+    * `service.instance.id` is required for certain panes to light up
+  * `telemetry.sdk.language=java` is required to see data in the JVM section 
 
 ## Traces [#traces]
 

diff --git a/...telemetry-integrations/opentelemetry/view-your-opentelemetry-data-new-relic.mdx b/...telemetry-integrations/opentelemetry/view-your-opentelemetry-data-new-relic.mdx
@@ -219,6 +219,16 @@ For your data to appear in this section, make sure it has the following:
     </tbody>
 </table>
 
+### Errors [#errors]
+
+On the Errors page, you can see total errors as well as charts showing error count and error rate.
+
+For your data to appear in this section, make sure it has the following:
+
+  * `span.kind = server` or `consumer`
+  * `otel.status_code = ERROR`
+  * Facets by span name
+
 ### Externals [#externals]
 
 Externals capture calls to out-of-process services such as web services, resources in the cloud, and other network entities.