[docs/collector/internal-telemetry.md] Clarify that configuration schema is unstable (#6219)

Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Alex Boten <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>

Author: 4 people

content/en/docs/collector/internal-telemetry.md

@@ -10,6 +10,18 @@ configure it to help you
 [monitor](#use-internal-telemetry-to-monitor-the-collector) and
 [troubleshoot](/docs/collector/troubleshooting/) the Collector.
 
+{{% alert title="Important" color="warning" %}} The Collector uses the
+OpenTelemetry SDK
+[declarative configuration schema](https://github.com/open-telemetry/opentelemetry-configuration)
+for configuring how to export its internal telemetry. This schema is still under
+[development](/docs/specs/otel/document-status/#lifecycle-status) and may
+undergo **breaking changes** in future releases. We intend to keep supporting
+older schemas until a 1.0 schema release is available, and offer a transition
+period for users to update their configurations before dropping pre-1.0 schemas.
+For details and to track progress see
+[issue #10808](https://github.com/open-telemetry/opentelemetry-collector/issues/10808).
+{{% /alert %}}
+
 ## Activate internal telemetry in the Collector
 
 By default, the Collector exposes its own telemetry in two ways:

static/refcache.json

@@ -6387,6 +6387,10 @@
     "StatusCode": 206,
     "LastSeen": "2025-02-01T07:12:43.673402-05:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-collector/issues/10808": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-05T17:17:50.215922389Z"
+  },
   "https://github.com/open-telemetry/opentelemetry-collector/issues/6151": {
     "StatusCode": 206,
     "LastSeen": "2025-02-01T07:12:51.032442-05:00"