Merge pull request #8254 from jack-berg/patch-2

Fix OpenTelemetry batching dead links
newrelic · Jun 29, 2022 · c67733e · c67733e
2 parents e9c55e8 + 919ed9b
commit c67733e
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/...grations/opentelemetry/best-practices/opentelemetry-best-practices-batching.mdx b/...grations/opentelemetry/best-practices/opentelemetry-best-practices-batching.mdx
@@ -11,8 +11,8 @@ metaDescription: Here are some tips for working with OpenTelemetry batching and
   To avoid getting rate limited, we recommend these practices:
 
   * Batch requests sent to the OTLP endpoint as described in this section
-  * Explicitly enable [gzip compression](#compression)
-  * Ensure your [attribute lengths](#attribute-lengths) don't exceed New Relic maximums
+  * Explicitly enable [gzip compression](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-compression)
+  * Ensure your [attribute lengths](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-attributes) don't exceed New Relic maximums
 </Callout>
 
 By default, the OpenTelemetry SDKs and Collector send one (1) data point per request. Using these defaults, it is likely your account will be rate limited.
@@ -73,4 +73,4 @@ All OpenTelemetry SDKs and Collectors provide a `BatchProcessor`, which batches
       </td>
     </tr>
   </tbody>
-</table>
+</table>