remove the properties that can't be read with the java agent

Author: zeitlinger

docs/misc/declarative-configuration/config.yaml

@@ -7,12 +7,6 @@
 # - https://github.com/open-telemetry/opentelemetry-configuration/blob/main/examples/sdk-migration-config.yaml
 # - https://github.com/open-telemetry/opentelemetry-configuration/blob/main/examples/sdk-config.yaml
 
-# Re-use this flag to disable the Agent/Spring starter as well as the SDK.
-# Note that the Agent/Spring starter still keeps the convention to use "enabled" -
-# this is just an exception to the rule.
-disabled: false # was: "otel.javaagent.enabled"
-# Re-use this flag from the SDK: if value is "debug", we trigger the behavior of "otel.javaagent.debug"
-log_level: info # was: "otel.javaagent.debug"
 instrumentation/development:
   # nothing changes here - just for reference
   general:
@@ -54,12 +48,6 @@ instrumentation/development:
       exclude_class_loaders: # was "otel.javaagent.exclude-class-loaders"
         - a
         - b
-      logging:
-        # was "otel.javaagent.logging"
-        output:
-          application:
-            logs_buffer_max_records: 1000 # can only be used with "type: application"
-          simple: # mutually exclusive with "application"
     common:
       default:
         enabled: true # was "otel.instrumentation.common.default-enabled"
@@ -69,3 +57,8 @@ instrumentation/development:
         # disabled by default
         # enabled applies to both spans and logs (but not metrics due to high cardinality)
         enabled: true # was "otel.javaagent.add-thread-details" = "true"
+
+# These cannot be used in the Java Agent, because they are read in early stages,
+# but the Spring starter can use them.
+disabled: false # was: "otel.sdk.enabled"
+log_level: info # is not used is Spring starter yet