Move OTel support levels to Compatibility page

content/en/opentelemetry/compatibility.md

@@ -87,6 +87,16 @@ For more information, see [Cloud Network Monitoring Setup][3].
 
 For unsupported languages in OpenTelemetry setups, [configure telemetry tagging][5] to link data to a specific commit.
 
+## Support levels
+
+Datadog provides different levels of support for OpenTelemetry components and configurations:
+
+- **Datadog Supported Components**: Datadog-owned components such as the [Datadog Connector][39], [Datadog Exporter][40], and [Infra Attribute Processor][41]. These components are maintained by Datadog, receive regular updates, and are prioritized for bug fixes and feature enhancements.
+
+- **Community Supported Components**: OpenTelemetry components [included with the DDOT Collector][42] by default. Datadog helps ensure these components are secure, stable, and compatible.
+
+- **Custom Components**: OpenTelemetry components or configurations not included by default, such as [custom Collector components][43] or [instrumentation of unsupported runtimes][44]. Datadog provides guidance and documentation as a starting point but does not directly support these components' functionality. For issues with custom components, engage with the [OpenTelemetry community][45] or the component maintainers.
+
 ## Platform and environment support
 
 While the OpenTelemetry Collector can be deployed in many environments, certain platforms have specific limitations or support requirements.
@@ -144,3 +154,10 @@ When using Datadog and OpenTelemetry together, Datadog recommends the following
 [36]: /opentelemetry/instrument/api_support/ruby/
 [37]: /opentelemetry/instrument/api_support/php/
 [38]: /llm_observability/instrumentation/otel_instrumentation/
+[39]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/connector/datadogconnector/README.md
+[40]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/datadogexporter/README.md
+[41]: https://github.com/DataDog/datadog-agent/tree/main/comp/otelcol/otlp/components/processor/infraattributesprocessor#readme
+[42]: /opentelemetry/setup/ddot_collector/#opentelemetry-collector-components
+[43]: /opentelemetry/setup/ddot_collector/custom_components
+[44]: /opentelemetry/guide/instrument_unsupported_runtimes
+[45]: https://opentelemetry.io/community/

content/en/opentelemetry/guide/instrument_unsupported_runtimes.md

@@ -21,7 +21,7 @@ This guide walks through instrumenting a [Bun][2] application as an example. Bun
 ## Support level
 
 <div class="alert alert-info">
-This guide falls under the <strong>Custom Components</strong> <a href="/opentelemetry/setup/ddot_collector#support-levels">support level</a>. Datadog provides this documentation as a starting point, but does not directly support the runtime's functionality or the OpenTelemetry SDK's behavior within it. For runtime-specific issues, engage with the <a href="https://opentelemetry.io/community/">OpenTelemetry community</a> or the runtime maintainers.
+This guide falls under the <strong>Custom Components</strong> <a href="/opentelemetry/compatibility/#support-levels">support level</a>. Datadog provides this documentation as a starting point, but does not directly support the runtime's functionality or the OpenTelemetry SDK's behavior within it. For runtime-specific issues, engage with the <a href="https://opentelemetry.io/community/">OpenTelemetry community</a> or the runtime maintainers.
 </div>
 
 ## Prerequisites

content/en/opentelemetry/setup/ddot_collector/_index.md

@@ -65,13 +65,7 @@ The DDOT Collector offers:
 
 ### Support levels
 
-Datadog provides different levels of support depending on the type of component:
-
-- **Datadog Supported Components**: Datadog-owned components such as the [Datadog Connector][44], [Datadog Exporter][38], and [Infra Attribute Processor][50]. These components are maintained by Datadog, receive regular updates, and are prioritized for bug fixes and feature enhancements within OpenTelemetry community guidelines.
-
-- **Community Supported Components**: [OpenTelemetry components](#opentelemetry-collector-components) included with the Agent by default. Datadog ensures these components are secure, stable, and compatible with the Agent.
-
-- **Custom Components**: OpenTelemetry components that are not included with the Agent by default and are added through the [custom components process][2]. Datadog provides guidance on the integration process but does not provide direct support for these components' functionality. For issues with custom components, Datadog recommends engaging with the OpenTelemetry community or the component maintainers.
+For details on Datadog, community, and custom component support, see [Support levels][57] on the Compatibility page.
 
 ### OpenTelemetry Collector components
 
@@ -233,3 +227,4 @@ This guide helps you migrate from an existing OpenTelemetry Collector setup to t
 [54]: /getting_started/tagging/unified_service_tagging/?tab=kubernetes
 [55]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/loadbalancingexporter/README.md
 [56]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/connector/routingconnector/README.md
+[57]: /opentelemetry/compatibility/#support-levels