Merge branch 'main' into fix/zapgrpc-client-close-warning

Author: kruthiwusirika5

.chloggen/14411.yaml

@@ -0,0 +1,48 @@
+# 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. receiver/otlp)
+component: all
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add declarative schema support for service telemetry resource configuration.
+
+# One or more tracking issues or pull requests related to the change
+issues: [14411]
+
+# (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: |
+  The `service::telemetry::resource` configuration now accepts the declarative schema with explicit name/value pairs:
+  ```yaml
+  service:
+    telemetry:
+      resource:
+        schema_url: https://opentelemetry.io/schemas/1.38.0
+        attributes:
+          - name: service.name
+            value: my-collector
+          - name: host.name
+            value: collector-host
+  ```
+
+  The legacy inline attribute map format is still supported for backward compatibility:
+  ```yaml
+  service:
+    telemetry:
+      resource:
+        service.name: my-collector
+        host.name: collector-host
+  ```
+
+  Note: `resource.detectors` is accepted for forward compatibility but is not yet applied by the collector.
+
+# 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]

.chloggen/add-endpoint-to-otlpexporter-metrics.yaml

@@ -0,0 +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
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
+component: exporter/otlp_grpc
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Added the `server.address` and `url.path` attributes to metrics generated by the otlp exporter.
+
+# One or more tracking issues or pull requests related to the change
+issues: [14998]
+
+# (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: ["user"]

.chloggen/add-endpoint-to-otlphttpexporter-metrics.yaml

@@ -0,0 +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
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
+component: exporter/otlp_http
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Added the `server.address` and `url.path` attributes to metrics generated by the otlp_http exporter.
+
+# One or more tracking issues or pull requests related to the change
+issues: [14998]
+
+# (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: ["user"]

.chloggen/aix_tier3.yaml .chloggen/codeboten_fg-stabilize.yaml.chloggen/aix_tier3.yaml renamed to .chloggen/codeboten_fg-stabilize.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: 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: pkg/confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Move aix/ppc64 to tier 3 support
+note: Stabilize framedSnappy feature gate.
 
 # One or more tracking issues or pull requests related to the change
-issues: [13380]
+issues: [15096]
 
 # (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/config.yaml

@@ -12,16 +12,13 @@ components:
     - cmd/mdatagen
     - connector/forward
     - connector/sample
-    - consumer/consumererror/xconsumererror
-    - consumer/xconsumer
     - docs/rfcs
     - exporter/debug
     - exporter/nop
     - exporter/otlp_grpc
     - exporter/otlp_http
     - extension/memory_limiter
     - extension/zpages
-    - pdata/pprofile
     - pkg/client
     - pkg/component
     - pkg/component/componentstatus
@@ -44,6 +41,7 @@ components:
     - pkg/consumer
     - pkg/consumer/consumererror
     - pkg/consumer/consumertest
+    - pkg/consumererror/xconsumererror
     - pkg/exporter
     - pkg/exporter/exportertest
     - pkg/exporterhelper
@@ -56,10 +54,12 @@ components:
     - pkg/extensionmiddleware/extensionmiddlewaretest
     - pkg/featuregate
     - pkg/filter
+    - pkg/graph
     - pkg/otelcol
     - pkg/otelcol/otelcoltest
     - pkg/pdata
     - pkg/pipeline
+    - pkg/pprofile
     - pkg/processor
     - pkg/processor/processortest
     - pkg/processorhelper
@@ -75,6 +75,7 @@ components:
     - pkg/service/telemetry/telemetrytest
     - pkg/xconfmap
     - pkg/xconnector
+    - pkg/xconsumer
     - pkg/xexporter
     - pkg/xexporterhelper
     - pkg/xextension
@@ -100,4 +101,3 @@ components:
     - receiver/sample
     - receiver/sampleentity
     - scraper/sample
-    - service/graph

.chloggen/configgrpc-balancername.yaml

@@ -0,0 +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
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
+component: pkg/config/configgrpc
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add a `DefaultBalancerName` constant for the name of the default load balancer
+
+# One or more tracking issues or pull requests related to the change
+issues: [15139]
+
+# (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 replaces the `BalancerName` function.
+
+# 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]

.chloggen/configgrpc-resolver-scheme.yaml

@@ -0,0 +1,28 @@
+# 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. receiver/otlp)
+component: pkg/config/configgrpc
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution
+
+# One or more tracking issues or pull requests related to the change
+issues: [14990]
+
+# (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: |
+  After the migration to grpc.NewClient, some gRPC client components such as the OTLP
+  exporter experienced connection issues in dual-stack DNS environments. This can now be
+  fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field.
+
+# 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, api]

.chloggen/confignet-npipe.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: pkg/config/confignet
+note: Add support for Windows Named Pipe (npipe) transport
+issues: [15085]

.chloggen/go_validators_mdatagen.yaml …ggen/default_config_values_mdatagen.yaml.chloggen/go_validators_mdatagen.yaml renamed to .chloggen/default_config_values_mdatagen.yaml .chloggen/go_validators_mdatagen.yaml renamed to .chloggen/default_config_values_mdatagen.yaml

@@ -7,10 +7,10 @@ change_type: enhancement
 component: cmd/mdatagen
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Added ability to generate required fields validation to config go structs generated by mdatagen
+note: Handle default values for configuration fields in generated code in mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [14563]
+issues: [14560]
 
 # (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/extra-attributes-for-exporters.yaml

@@ -0,0 +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
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
+component: pkg/exporterhelper
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Added the `WithAttrs` option to allow custom attributes on exporter metrics
+
+# One or more tracking issues or pull requests related to the change
+issues: [14998]
+
+# (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"]