Merge branch 'main' into axw-emeritus

Author: axw

.chloggen/14311-1.yaml

@@ -93,6 +93,7 @@ components:
     - pkg/xscraperhelper
     - processor/batch
     - processor/memory_limiter
+    - processor/queuebatch
     - processor/sample
     - provider/env
     - provider/file

.chloggen/batchprocessor-batch-send-size-bytes-buckets.yaml

@@ -1,23 +1,25 @@
+# Use this changelog template to create an entry for release notes.
+
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: pkg/featuregate
+component: pkg/confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix panic when a `--feature-gates` value contains an empty comma-separated element (e.g. `--feature-gates=alpha,`)
+note: Make `configauth.Config` a named field of `AuthConfig` instead of an embedded one.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15536]
+issues: [15308]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
-subtext: An empty identifier now produces a returned error instead of an index-out-of-range panic during flag parsing.
+subtext: |
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # Include 'user' if the change is relevant to end users.
 # Include 'api' if there is a change to a library API.
 # Default: '[user]'
-change_logs: [user]
+change_logs: [api]

.chloggen/config.yaml

@@ -0,0 +1,13 @@
+change_type: enhancement
+
+component: pkg/exporterhelper
+
+note: Add the `pkg.exporterhelper.queueBatchEnabled` feature gate
+
+issues: [14038, 13582, 12022]
+
+subtext: |
+  When enabled, the batch settings returned by `NewDefaultQueueConfig()` have
+  `batch::enabled` true. See [migration RFC](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/batching-migration.md#phase-1).
+
+change_logs: [user]

…oggen/fix-featuregate-empty-element.yaml …loggen/confighttp-auth-named-config.yaml.chloggen/fix-featuregate-empty-element.yaml renamed to .chloggen/confighttp-auth-named-config.yaml .chloggen/fix-featuregate-empty-element.yaml renamed to .chloggen/confighttp-auth-named-config.yaml

@@ -1,23 +1,25 @@
+# Use this changelog template to create an entry for release notes.
+
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: exporter/debug
+component: pkg/config/configretry
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix the scope index printed by the `normal` verbosity marshaler; each scope was labelled with its parent resource's index instead of its own position
+note: Migrate `BackOffConfig` to schema-based configuration generated by mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15541]
+issues: [15502]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
-subtext: Affected all four signals (logs, traces, metrics, profiles) — e.g. the second scope under a resource printed `#0` instead of `#1`.
+subtext:
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # Include 'user' if the change is relevant to end users.
 # Include 'api' if there is a change to a library API.
 # Default: '[user]'
-change_logs: [user]
+change_logs: [api]

.chloggen/exporterhelper-queue-batch-gate.yaml

@@ -1,16 +1,16 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: new_component
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: pkg/config/configstorage
+component: pkg/config/configtls
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add a new configstorage module to support storage configuration fields.
+note: Migrate `TLS` core types to schema-based configuration generated by mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [5832]
+issues: [15693]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.

.chloggen/exporterhelper-queue-batch-send-size-bytes-buckets.yaml

@@ -1,29 +1,25 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: all
+component: extension/zpages
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Bootstrap `config.schema.yaml` for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC.
+note: Make `confighttp.ServerConfig` a named field of `Config` instead of an embedded one.
 
 # One or more tracking issues or pull requests related to the change
-issues: [14543]
+issues: [15308]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-  Schemas are generated using the `schemagen` tool from opentelemetry-collector-contrib and hand-tuned to capture
-  validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper,
-  etc.). A `.schemagen.yaml` settings file and a `generate-schemas` Makefile target are added so the schemas can
-  be regenerated reproducibly.
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # Include 'user' if the change is relevant to end users.
 # Include 'api' if there is a change to a library API.
 # Default: '[user]'
-change_logs: [user]
+change_logs: [api]

…ix-debugexporter-normal-scope-index.yaml .chloggen/migrate_configretry.yaml.chloggen/fix-debugexporter-normal-scope-index.yaml renamed to .chloggen/migrate_configretry.yaml .chloggen/fix-debugexporter-normal-scope-index.yaml renamed to .chloggen/migrate_configretry.yaml

@@ -99,6 +99,7 @@ processor/memorylimiterprocessor/                      @open-telemetry/collector
 processor/processorhelper/                             @open-telemetry/collector-approvers
 processor/processorhelper/xprocessorhelper/            @open-telemetry/collector-approvers
 processor/processortest/                               @open-telemetry/collector-approvers
+processor/queuebatchprocessor/                         @open-telemetry/collector-approvers @jmacd @iblancasa
 processor/xprocessor/                                  @open-telemetry/collector-approvers @mx-psi @dmathieu
 receiver/                                              @open-telemetry/collector-approvers
 receiver/nopreceiver/                                  @open-telemetry/collector-approvers @evan-bradley