diff --git a/.chloggen/codeboten_update-units-processorhelper.yaml b/.chloggen/codeboten_update-units-processorhelper.yaml
deleted file mode 100644
index c352ec40509..00000000000
--- a/.chloggen/codeboten_update-units-processorhelper.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: processorhelper
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: update units for internal telemetry
-
-# One or more tracking issues or pull requests related to the change
-issues: [10647]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/componenttest-extra-attributes.yaml b/.chloggen/componenttest-extra-attributes.yaml
deleted file mode 100644
index 3683ca634b2..00000000000
--- a/.chloggen/componenttest-extra-attributes.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: component/componenttest
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add optional ...attribute.KeyValue argument to TestTelemetry.CheckExporterMetricGauge.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10593]
-
-# 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: [api]
diff --git a/.chloggen/confmap-increase-recursive-count.yaml b/.chloggen/confmap-increase-recursive-count.yaml
deleted file mode 100644
index cf8a8fe479a..00000000000
--- a/.chloggen/confmap-increase-recursive-count.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confmap
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Increase the amount of recursion and URI expansions allowed in a single line
-
-# One or more tracking issues or pull requests related to the change
-issues: [10712]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/document_factories.yaml b/.chloggen/document_factories.yaml
deleted file mode 100644
index fffb842e1b6..00000000000
--- a/.chloggen/document_factories.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: exporter, processor, receiver
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Document factory functions.
-
-# One or more tracking issues or pull requests related to the change
-issues: [9323]
-
-# (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:
-
-# 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: [api]
diff --git a/.chloggen/document_fields.yaml b/.chloggen/document_fields.yaml
deleted file mode 100644
index cd2af1bcb6c..00000000000
--- a/.chloggen/document_fields.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: component
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Document status enums and New constructors
-
-# One or more tracking issues or pull requests related to the change
-issues: [9822]
-
-# (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:
-
-# 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: [api]
diff --git a/.chloggen/experimental_include_metadata.yaml b/.chloggen/experimental_include_metadata.yaml
deleted file mode 100644
index 11a936f5b8d..00000000000
--- a/.chloggen/experimental_include_metadata.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confighttp, configgrpc
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Remove the experimental comment on `IncludeMetadata` in confighttp and configgrpc
-
-# One or more tracking issues or pull requests related to the change
-issues: [9381]
-
-# (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:
-
-# 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: [api]
diff --git a/.chloggen/exporterhelper-report-data-type-in-queue-metrics.yaml b/.chloggen/exporterhelper-report-data-type-in-queue-metrics.yaml
deleted file mode 100644
index e4065d6e4bc..00000000000
--- a/.chloggen/exporterhelper-report-data-type-in-queue-metrics.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: exporterhelper
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add data_type attribute to `otelcol_exporter_queue_size` metric to report the type of data being processed.
-
-# One or more tracking issues or pull requests related to the change
-issues: [9943]
-
-# 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]
diff --git a/.chloggen/exporterhelper_metric_units.yaml b/.chloggen/exporterhelper_metric_units.yaml
deleted file mode 100644
index de6a645ffe3..00000000000
--- a/.chloggen/exporterhelper_metric_units.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: exporterhelper
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Update units for internal telemetry
-
-# One or more tracking issues or pull requests related to the change
-issues: [10648]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/fix-env-var-double-escaping.yaml b/.chloggen/fix-env-var-double-escaping.yaml
deleted file mode 100644
index 5ea730a1965..00000000000
--- a/.chloggen/fix-env-var-double-escaping.yaml
+++ /dev/null
@@ -1,27 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confmap
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix wrong expansion of environment variables escaped with `$$`, e.g. `$${ENV_VAR}` and `$$ENV_VAR`.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10713]
-
-# (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: |
-  This change fixes the issue where environment variables escaped with $$ were expanded. 
-  The collector now converts `$${ENV_VAR}` to `${ENV_VAR}` and `$$ENV_VAR` to `$ENV_VAR` without further expansion.
-
-# 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: [api]
diff --git a/.chloggen/jpkroehling-grpc-statuscode.yaml b/.chloggen/jpkroehling-grpc-statuscode.yaml
deleted file mode 100644
index d78ef4c7a9a..00000000000
--- a/.chloggen/jpkroehling-grpc-statuscode.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: 'enhancement'
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: configgrpc
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: gRPC auth errors now return gRPC status code UNAUTHENTICATED (16)
-
-# One or more tracking issues or pull requests related to the change
-issues: [7646]
-
diff --git a/.chloggen/mx-psi_string-value-for-string-fields.yaml b/.chloggen/mx-psi_string-value-for-string-fields.yaml
deleted file mode 100644
index 0a7a49175c4..00000000000
--- a/.chloggen/mx-psi_string-value-for-string-fields.yaml
+++ /dev/null
@@ -1,27 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confmap
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: When passing configuration for a string field using any provider, use the verbatim string representation as the value.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10605, 10405]
-
-# (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: | 
-  This matches the behavior of `${ENV}` syntax prior to the promotion of the `confmap.unifyEnvVarExpansion` feature gate
-  to beta. It changes the behavior of the `${env:ENV}` syntax with escaped strings.
-
-# 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: []
diff --git a/.chloggen/mx-psi_validate-uris.yaml b/.chloggen/mx-psi_validate-uris.yaml
deleted file mode 100644
index 69af525d77d..00000000000
--- a/.chloggen/mx-psi_validate-uris.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: httpprovider, httpsprovider
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Validate URIs in HTTP and HTTPS providers before fetching.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10468]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/profiles-consumertest.yaml b/.chloggen/profiles-consumertest.yaml
deleted file mode 100644
index b211551f461..00000000000
--- a/.chloggen/profiles-consumertest.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: consumer/consumertest
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Allow testing profiles with consumertest.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10692]
-
-# (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:
-
-# 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: [api]
diff --git a/.chloggen/receiverhelper_metric_units.yaml b/.chloggen/receiverhelper_metric_units.yaml
deleted file mode 100644
index 3f06210459e..00000000000
--- a/.chloggen/receiverhelper_metric_units.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: receiverhelper
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Update units for internal telemetry
-
-# One or more tracking issues or pull requests related to the change
-issues: [10650]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/scraperhelper_metric_units.yaml b/.chloggen/scraperhelper_metric_units.yaml
deleted file mode 100644
index 3e754f6a991..00000000000
--- a/.chloggen/scraperhelper_metric_units.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: scraperhelper
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Update units for internal telemetry
-
-# One or more tracking issues or pull requests related to the change
-issues: [10649]
-
-# (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:
-
-# 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: []
diff --git a/.chloggen/service-remove-ballast-deps-2.yaml b/.chloggen/service-remove-ballast-deps-2.yaml
deleted file mode 100644
index e6377b387de..00000000000
--- a/.chloggen/service-remove-ballast-deps-2.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: processor/memorylimiter
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The memory limiter processor will no longer account for ballast size.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10696]
-
-# (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: If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.
-
-# 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: []
diff --git a/.chloggen/service-remove-ballast-deps-3.yaml b/.chloggen/service-remove-ballast-deps-3.yaml
deleted file mode 100644
index c07f90439f6..00000000000
--- a/.chloggen/service-remove-ballast-deps-3.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: extension/memorylimiter
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The memory limiter extension will no longer account for ballast size.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10696]
-
-# (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: If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.
-
-# 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: []
diff --git a/.chloggen/service-remove-ballast-deps.yaml b/.chloggen/service-remove-ballast-deps.yaml
deleted file mode 100644
index 31ffa90c3ac..00000000000
--- a/.chloggen/service-remove-ballast-deps.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
-
-# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: service
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The service will no longer be able to get a ballast size from the deprecated ballast extension.
-
-# One or more tracking issues or pull requests related to the change
-issues: [10696]
-
-# (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: If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.
-
-# 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: []
diff --git a/cmd/mdatagen/go.mod b/cmd/mdatagen/go.mod
index 3f61958580d..2239a1f5615 100644
--- a/cmd/mdatagen/go.mod
+++ b/cmd/mdatagen/go.mod
@@ -81,6 +81,8 @@ replace go.opentelemetry.io/collector/semconv => ../../semconv
 
 replace go.opentelemetry.io/collector/featuregate => ../../featuregate
 
+replace go.opentelemetry.io/collector/consumer => ../../consumer
+
 replace go.opentelemetry.io/collector => ../..
 
 replace go.opentelemetry.io/collector/config/configtelemetry => ../../config/configtelemetry