Merge branch 'main' into main

.chloggen/add_unsupported_platforms.yaml → .chloggen/bnchmk-zstd.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: mdatagen
+component: confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Adds unsupported platforms to the README header
+note: Disable concurrency in zstd compression
 
 # One or more tracking issues or pull requests related to the change
-issues: [9794]
+issues: [8216]
 
 # (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/configtls-remove-deprecated.yaml → .chloggen/codeboten_dep-context-methods.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: breaking
+change_type: deprecation
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: configtls
+component: confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Remove Deprecated `TLSSetting`, `TLSClientSetting`, and `TLSServerSetting`.
+note: deprecate ToClientContext, ToServerContext, ToListenerContext, replaced by ToClient, ToServer, ToListener
 
 # One or more tracking issues or pull requests related to the change
-issues: [9786]
+issues: [9807]
 
 # (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/fix-validate-command.yaml → .chloggen/codeboten_fix-sampler-typo.yaml

@@ -4,13 +4,13 @@
 change_type: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: otelcol
+component: service
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix issue where the `validate` command wasn't properly printing valid component type.
+note: fix record sampler configuration
 
 # One or more tracking issues or pull requests related to the change
-issues: [9866]
+issues: [9968]
 
 # (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/fix-componets-command.yaml → .chloggen/codeboten_use-config-sdk.yaml

@@ -4,13 +4,13 @@
 change_type: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: component
+component: service
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix issue where the `components` command wasn't properly printing the component type.
+note: ensure the tracer provider is configured via go.opentelemetry.io/contrib/config
 
 # One or more tracking issues or pull requests related to the change
-issues: [9856]
+issues: [9967]
 
 # (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/configtls-remove-deprecated2.yaml → .chloggen/configtls-add-newdefault-funcs.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: breaking
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: configtls
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Rename `TLSSetting` to `Config` on `ClientConfig` and `ServerConfig`.
+note: Adds `NewDefault*` functions for all the config structs.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9786]
+issues: [9658]
 
 # (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/configtls-add-context-to-public-funcs.yaml → .chloggen/configtls-depr-context-funcs.yaml

@@ -7,10 +7,10 @@ change_type: deprecation
 component: configtls
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate `ClientConfig.LoadTLSConfig` and `ServerConfig.LoadTLSConfig`, use `ClientConfig.LoadTLSConfigContext` and `ServerConfig.LoadTLSConfigContext` instead.
+note: Deprecates `ClientConfig.LoadTLSConfigContext` and `ServerConfig.LoadTLSConfigContext`, use `ClientConfig.LoadTLSConfig` and `ServerConfig.LoadTLSConfig` instead.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9811]
+issues: [9945]
 
 # (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/embedded_unmarshaler.yaml → .chloggen/mdatagen-filter.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confmap
+component: "cmd/mdatagen"
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Clarify the use of embedded structs to make unmarshaling composable
+note: "support excluding some metrics based on string and regexes in resource_attributes"
 
 # One or more tracking issues or pull requests related to the change
-issues: [7101]
+issues: [9661]
 
 # (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.
@@ -22,4 +22,4 @@ subtext:
 # 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: []
+change_logs: [user]

.chloggen/validate-otlpexporter-port.yaml → .chloggen/mdatagen-introduce-config-factory-tests.yaml

@@ -4,18 +4,19 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: otlpexporter
+component: cmd/mdatagen
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Checks for port in the config validation for the otlpexporter
+note: Generate config and factory tests covering their requirements.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9505]
+issues: [9940]
 
 # (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:
+subtext: |
+  The tests are moved from cmd/builder.
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'

.chloggen/codeboten_use-period.yaml → .chloggen/update-internal-metric-levels.yaml

@@ -4,26 +4,34 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: service
+component: telemetry
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: emit internal collector metrics with _ instead of / with OTLP export
+note: Distributed internal metrics across different levels.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9774]
+issues: [7890]
 
 # (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 is addressing an issue w/ the names of the metrics generated by the Collector for its
-  internal metrics. Note that this change only impacts users that emit telemetry using OTLP, which
-  is currently still in experimental support. The prometheus metrics already replaced `/` with `_`
-  and they will do the same with `_`.
+    The internal metrics levels are updated along with reported metrics:
+    - The default level is changed from `basic` to `normal`, which can be overridden with `service::telmetry::metrics::level` configuration.
+    - Batch processor metrics are updated to be reported starting from `normal` level:
+      - `processor_batch_batch_send_size` 
+      - `processor_batch_metadata_cardinality`
+      - `processor_batch_timeout_trigger_send`
+      - `processor_batch_size_trigger_send`
+    - GRPC/HTTP server and client metrics are updated to be reported starting from `detailed` level:
+      - http.client.* metrics
+      - http.server.* metrics
+      - rpc.server.* metrics
+      - rpc.client.* metrics
 
 # 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: []
+change_logs: [user]