Merge branch 'main' into kafka-receiver-backoff

* main: (111 commits)
  fix(azuremonitorreceiver): Azure Monitor receiver should not produce gaps in data points for PT1M time grains (#37342)
  fix(deps): update module sigs.k8s.io/controller-runtime to v0.20.2 (#37996)
  fix(deps): update module github.com/hashicorp/consul/api to v1.31.2 (#38031)
  [processor/resourcedetection] add instructions for recommended use of the dynatrace detector (#37962)
  fix(deps): update module github.com/go-sql-driver/mysql to v1.9.0 (#38007)
  fix(deps): update module google.golang.org/api to v0.221.0 (#38027)
  prometheusreceiver: deprecate start time adjustment (#37879)
  fix(deps): update module github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common to v1.0.1100 (#37995)
  chore(deps): update golang docker tag to v1.24 (#37997)
  fix(deps): update all github.com/aws packages (#37983)
  chore(deps): update prom/prometheus docker tag to v3.2.0 (#37998)
  fix(deps): update kubernetes packages to v0.32.2 (#38004)
  fix(deps): update module github.com/clickhouse/clickhouse-go/v2 to v2.32.1 (#38006)
  fix(deps): update module github.com/google/go-github/v69 to v69.2.0 (#38014)
  fix(deps): update module github.com/sap/go-hdb to v1.13.3 (#38021)
  fix(deps): update module go.etcd.io/bbolt to v1.4.0 (#38024)
  [exporter/stefexporter] Fix a context cancellation bug in STEF exporter (#37944)
  fix(deps): update module github.com/spf13/cobra to v1.9.1 (#38023)
  fix(deps): update module github.com/envoyproxy/go-control-plane/envoy to v1.32.4 (#37990)
  fix(deps): update module github.com/hashicorp/consul/api to v1.31.1 (#37991)
  ...

Author: yiquanzhou

.chloggen/add-global-conditions-and-group-error-mode-support.yaml

@@ -1,27 +1,27 @@
-# Use this changelog template to create an entry for release notes.
-
-# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: new_component
-
-# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: bmchelixexporter
-
-# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Mark the BMC Helix exporter as Alpha.
-
-# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36773]
-
-# (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]
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: new_component
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: azureblobexporter
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add new exporter for sending telemetry to Azure Storage Blob
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [35717]
+
+# (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/add-initial-buffer.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: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: datadogreceiver
+component: azuremonitorreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Implement support for span links
+note: "Fix bug where the time grain wasn't honored"
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [37449]
+issues: [37337]
 
 # (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.
@@ -25,3 +25,4 @@ subtext:
 # Include 'api' if there is a change to a library API.
 # Default: '[user]'
 change_logs: [user]
+

.chloggen/add-more-vecenter-receiver-virtual-machine-preformace-metrics.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. filelogreceiver)
-component: bearertokenauthextension
+component: kafkametricsreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Load token lazily for gRPC AUTH to fix token refresh issue
+note: Fix incorrect cluster admin initialization in consumer scraper
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36749]
+issues: [36818]
 
 # (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.