Merge branch 'main' into fix-zookeeper-avg-latency-float

Author: vyagh

…iver-raw-xml-unmarshal-optimization.yaml .chloggen/45837-enable-keepalive.yaml.chloggen/wevtlog-receiver-raw-xml-unmarshal-optimization.yaml renamed to .chloggen/45837-enable-keepalive.yaml .chloggen/wevtlog-receiver-raw-xml-unmarshal-optimization.yaml renamed to .chloggen/45837-enable-keepalive.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
-component: pkg/stanza
+component: extension/health_check
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Optimizing the performance of Windows Event log unmarshalling when raw = true
+note: Enable keep-alives for the health check extension's HTTP and gRPC servers.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [47164]
+issues: [45837]
 
 # (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.

…ivedirectoryds-enable-reaggregation.yaml …n/46350-chrony-enable-reaggregation.yaml.chloggen/46346-activedirectoryds-enable-reaggregation.yaml renamed to .chloggen/46350-chrony-enable-reaggregation.yaml .chloggen/46346-activedirectoryds-enable-reaggregation.yaml renamed to .chloggen/46350-chrony-enable-reaggregation.yaml

@@ -4,13 +4,13 @@
 change_type: 'enhancement'
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
-component: receiver/active_directory_ds
+component: receiver/chrony
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Enables dynamic metric reaggregation in the Active Directory Domain Services receiver. This does not break existing configuration files.
+note: Enables dynamic metric reaggregation in the Chrony receiver. This does not break existing configuration files.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [46346]
+issues: [46350]
 
 # (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/46365-mongodbatlas-enable-reaggregation.yaml

@@ -0,0 +1,27 @@
+# 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/filelog)
+component: receiver/mongodb_atlas
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Enables dynamic metric reaggregation in the MongoDB Atlas receiver. This does not break existing configuration files.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [46365]
+
+# (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 your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# 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/46368-nginx-enable-reaggregation.yaml

@@ -0,0 +1,6 @@
+change_type: enhancement
+component: receiver/nginx
+note: Enable the re-aggregation feature for the nginx receiver
+issues: [46368]
+subtext:
+change_logs: [user]

.chloggen/46382-tcpcheck-enable-reaggregation.yaml

@@ -0,0 +1,27 @@
+# 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/filelog)
+component: receiver/tcpcheck
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Enables dynamic metric reaggregation in the TCP Check receiver. This does not break existing configuration files.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [46382]
+
+# (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 your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# 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]

…en/exporter-datadog-sketch-pool-fix.yaml …kareceiver-resume-paused-partitions.yaml.chloggen/exporter-datadog-sketch-pool-fix.yaml renamed to .chloggen/47118-kafkareceiver-resume-paused-partitions.yaml .chloggen/exporter-datadog-sketch-pool-fix.yaml renamed to .chloggen/47118-kafkareceiver-resume-paused-partitions.yaml

@@ -4,24 +4,25 @@
 change_type: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
-component: exporter/datadog
+component: receiver/kafka
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix use-after-free bug causing corrupted quantile sketches when exporting ExponentialHistogram metrics with multiple attribute sets
+note: Resume paused partitions after backoff delay and on reassignment after rebalance
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [47338]
+issues: [47118]
 
 # (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: |
-  When multiple ExponentialHistogram data points were converted to Datadog sketches in a single
-  export call, the underlying sync.Pool backing array was shared across conversions. A second
-  conversion would reuse and overwrite the first sketch's bin memory, producing non-monotonic
-  bin keys and inflated percentile values. This is fixed by upgrading
-  github.com/DataDog/datadog-agent/pkg/util/quantile to commit bfa4eff6c991, which deep-copies
-  the bin slice before returning the sketch.
+  When message_marking.after=true and message_marking.on_error=false, non-permanent
+  processing errors (e.g. from memorylimiter) caused PauseFetchPartitions to be called
+  but ResumeFetchPartitions was never called, leaving partitions paused forever.
+  Partitions are now automatically resumed after the configured error_backoff.initial_interval
+  delay when error_backoff is enabled. Additionally, partitions paused across rebalances
+  are resumed via ResumeFetchPartitions in the assigned callback, since franz-go persists
+  the pause state by design.
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/47119-sqlserver-query-sample-blocking-resource.yaml

@@ -0,0 +1,26 @@
+# 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/filelog)
+component: receiver/sqlserver
+
+# A brief description of the change. Surround your text with quotes (") if it needs to start with a backtick (`).
+note: Enriches `db.server.query_sample` log records in the SQL Server receiver with wait-derived fields by adding `sqlserver.blocking.start_time`, `sqlserver.wait.resource.type`, `sqlserver.wait.resource.id`, and `sqlserver.lock.type`.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [47119]
+
+# (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: "`sqlserver.blocking.start_time` is emitted only when `sqlserver.blocking_session_id` is positive; `sqlserver.wait.resource.type` and `sqlserver.wait.resource.id` are parsed from `wait_resource`; and `sqlserver.lock.type` maps lock waits to `shared`/`exclusive`."
+
+# 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/47173-bug-defaultConfigPrometheusExporter.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
-component: receiver/elasticsearch
+component: pkg/faro
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Enable dynamic attribute metric with attribute re-aggregation in configuration at runtime
+note: Translate new Faro payload fields Meta.Device, Meta.OS, App.InstallationID, and Exception.Fatal.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [46353]
+issues: [47708]
 
 # (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.

…-enable-reaggregation-elasticsearch.yaml …8-faro-device-os-installation-fatal.yaml.chloggen/feat_46462-enable-reaggregation-elasticsearch.yaml renamed to .chloggen/47708-faro-device-os-installation-fatal.yaml .chloggen/feat_46462-enable-reaggregation-elasticsearch.yaml renamed to .chloggen/47708-faro-device-os-installation-fatal.yaml

@@ -0,0 +1,5 @@
+change_type: enhancement
+component: pkg/batchperresourceattr
+note: Add `WithMetadataInjection()` option to inject batched resource attribute values as `client.Metadata` into the context passed to the next consumer.
+issues: [47695]
+change_logs: [api]