Merge remote-tracking branch 'upstream/main'

Author: kalvkusk

…ter-tinybird-limit-requests-to-10mb.yaml …s-in-prometheusremotewrite-receiver.yaml.chloggen/exporter-tinybird-limit-requests-to-10mb.yaml renamed to .chloggen/accept-unspecified-types-as-gauges-in-prometheusremotewrite-receiver.yaml .chloggen/exporter-tinybird-limit-requests-to-10mb.yaml renamed to .chloggen/accept-unspecified-types-as-gauges-in-prometheusremotewrite-receiver.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: tinybirdexporter
+component: prometheusremotewritereceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Limit request body to 10MB to avoid exceeding the EventsAPI size limit.
+note: Adds support to accept METRIC_TYPE_UNSPECIFIED as gauge type
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [41782]
+issues: [41840]
 
 # (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.

…en/fix-exp-hist-aggregation-offsets.yaml .chloggen/aws-s3-partition-timezone.yaml.chloggen/fix-exp-hist-aggregation-offsets.yaml renamed to .chloggen/aws-s3-partition-timezone.yaml .chloggen/fix-exp-hist-aggregation-offsets.yaml renamed to .chloggen/aws-s3-partition-timezone.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: coreinternal/aggregateutil
+component: exporter/awss3
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Aggregate exponential histogram data points when different offsets are present"
+note: Add S3PartitionTimezone config value to be able to change the timezone used for time-based partitioning
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [42412]
+issues: [42319]
 
 # (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/kubelet-volume-used.yaml …codeboten_bump-telemetrygen-semconv.yaml.chloggen/kubelet-volume-used.yaml renamed to .chloggen/codeboten_bump-telemetrygen-semconv.yaml .chloggen/kubelet-volume-used.yaml renamed to .chloggen/codeboten_bump-telemetrygen-semconv.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: receiver/kubeletstats
+component: telemetrygen
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Introduce k8s.pod.volume.usage metric."
+note: Updates the semconv to use 1.37.0
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [40476]
+issues: [42567]
 
 # (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.

…ggen/apache-req-connections-metrics.yaml …loggen/countconnector-pdata-upgrade.yaml.chloggen/apache-req-connections-metrics.yaml renamed to .chloggen/countconnector-pdata-upgrade.yaml .chloggen/apache-req-connections-metrics.yaml renamed to .chloggen/countconnector-pdata-upgrade.yaml

@@ -4,18 +4,18 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: apachereceiver
+component: countconnector
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add number of connections per async state metrics.
+note: Upgrade profiles proto to 1.8.0
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [41886]
+issues: [42526]
 
 # (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:
 
 # 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/cx-exporter-rate-limiter.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. filelogreceiver)
+component: coralogixexporter
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Enable rate limiter mechanism in the Coralogix exporter. To disable it set `rate_limiter.enabled` to `false`."
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [42552]
+
+# (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/mx-psi_interval-passing.yaml .chloggen/ddexporter-remove-zorkian.yaml.chloggen/mx-psi_interval-passing.yaml renamed to .chloggen/ddexporter-remove-zorkian.yaml

@@ -1,28 +1,29 @@
 # 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. filelogreceiver)
 component: datadogexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add alpha feature gate 'exporter.datadogexporter.InferIntervalForDeltaMetrics'.
+note: Deprecate zorkian codepath
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [42494]
+issues: [17373]
 
 # (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 feature gate will set the interval for OTLP delta metrics mapped by the exporter when it can infer them.
+subtext: |
+  Feature gate exporter.datadogexporter.metricexportnativeclient is now deprecated; the default metrics exporter is now 
+  Metrics Export Serializer unless feature gate exporter.datadogexporter.metricexportserializerclient is disabled. 
+  See https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.122.0 and #37930 for more 
+  info about Metrics Export Serializer. 
 
-# 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: []
+change_logs: [user, api]

.chloggen/dockerstatsreceiver-add-windows-support.yaml

@@ -1,22 +1,23 @@
 # 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: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: transformprocessor
+component: receiver/snowflake, receiver/sqlquery
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add support for merging histogram buckets.
+note: Fix panic on startup caused by gosnowflake `v1.16.0`
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [40280]
+issues: [42605]
 
 # (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 transformprocessor now supports merging histogram buckets using the `merge_histogram_buckets` function.
+  The solution was to downgrade the dependency version to `v1.15.0`.
+  For more information, refer to the [upstream gosnowflake issue](https://github.com/snowflakedb/gosnowflake/issues/1533)
 
 # 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/40280.yaml .chloggen/downgrade_snowflake_dep.yaml.chloggen/40280.yaml renamed to .chloggen/downgrade_snowflake_dep.yaml

@@ -7,10 +7,10 @@ change_type: bug_fix
 component: elasticsearchexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Ignore expected errors when making bulk requests to profiling indices.
+note: Fix a bug where data stream attributes in 'none' mapping mode have invalid prefix.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [38598]
+issues: [42454]
 
 # (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/issue-38598.yaml …exporter-fix-data-stream-attributes.yaml.chloggen/issue-38598.yaml renamed to .chloggen/elasticsearchexporter-fix-data-stream-attributes.yaml .chloggen/issue-38598.yaml renamed to .chloggen/elasticsearchexporter-fix-data-stream-attributes.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. filelogreceiver)
 component: elasticsearchexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Populate profiling-hosts index with resource attribute information.
+note: Upgrade profiles proto to 1.8.0
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [42220]
+issues: [42526]
 
 # (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.