Merge upstream/main into feat/oracledb-session-jvm-os

# Conflicts:
#	receiver/oracledbreceiver/internal/metadata/generated_metrics_test.go

Author: rluidash

.chloggen/40989-azuremonitor-custom-namespace-discovery.yaml

@@ -0,0 +1,13 @@
+change_type: bug_fix
+component: receiver/azure_monitor
+note: Fix discovery and collection of custom metric namespace definitions (e.g. `azure.vm.linux.guestmetrics` published by Azure Monitor Agent / MetricsExtension)
+issues: [40989]
+subtext: >
+  The MetricDefinitions API only returns custom namespace metrics when the
+  `metricnamespace` query parameter is explicitly set. Previously, metrics
+  configured under `receiver::metrics` for a custom namespace were silently
+  dropped because the API call used no filter and only returned the
+  resource's default namespace. The receiver now makes an additional
+  namespace-filtered call for each custom namespace in the `metrics` config
+  that was not returned by the default call.
+change_logs: [user]

.chloggen/47581-logdedup-metadata-keys.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: processor/log_dedup
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add `metadata_keys` and `metadata_cardinality_limit` options to support multi-tenant pipelines by aggregating logs into separate buckets per unique metadata combination and preserving request context for downstream extensions.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [47521]
+
+# (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: []

.chloggen/47740-httpcheck-dedup-tls-cert-remaining.yaml

@@ -0,0 +1,6 @@
+change_type: bug_fix
+component: receiver/http_check
+note: "Stop emitting two httpcheck.tls.cert_remaining data points per scrape"
+issues: [47740]
+subtext:
+change_logs: [user]

.chloggen/48365.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: bug_fix
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
+component: cmd/opampsupervisor
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Normalize merged `service.telemetry.resource` settings so mixed legacy inline attributes and declarative `attributes` entries do not produce invalid effective Collector configs"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [48365]
+
+# (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: []

.chloggen/48871-metricstransform-combine-validation.yaml

@@ -0,0 +1,24 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: bug_fix
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
+component: processor/metrics_transform
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Add required-field validation for `combine` action: return an error if `new_name` or `aggregation_type` is missing, preventing silent data loss and empty metric names."
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [48871]
+
+# (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.
+change_logs: [user]

.chloggen/48924-sovereign-gcp-monitoringreceiver.yaml

@@ -0,0 +1,9 @@
+change_type: enhancement
+
+component: receiver/googlecloudmonitoring
+
+note: Add `universe_domain` config option to support Sovereign Google Cloud regions. Setting this field passes `option.WithUniverseDomain` to the underlying Google API client.
+
+issues: [48924]
+
+change_logs: [user]

.chloggen/48924-sovereign-gcp-pubsubexporter.yaml

@@ -0,0 +1,9 @@
+change_type: enhancement
+
+component: exporter/googlecloudpubsub
+
+note: Add `universe_domain` config option to support Sovereign Google Cloud regions. Setting this field passes `option.WithUniverseDomain` to the underlying Google API client.
+
+issues: [48924]
+
+change_logs: [user]

.chloggen/48924-sovereign-gcp-pubsubreceiver.yaml

@@ -0,0 +1,9 @@
+change_type: enhancement
+
+component: receiver/googlecloudpubsub
+
+note: Add `universe_domain` config option to support Sovereign Google Cloud regions. Setting this field passes `option.WithUniverseDomain` to the underlying Google API client.
+
+issues: [48924]
+
+change_logs: [user]

.chloggen/48924-sovereign-gcp-storageexporter.yaml

@@ -0,0 +1,9 @@
+change_type: enhancement
+
+component: exporter/google_cloud_storage
+
+note: Add `universe_domain` config option to support Sovereign Google Cloud regions. Setting this field passes `option.WithUniverseDomain` to the underlying Google API client.
+
+issues: [48924]
+
+change_logs: [user]

.chloggen/49020-optimize-limit-buckets.yaml

@@ -0,0 +1,11 @@
+change_type: enhancement
+
+component: processor/transform
+
+note: Improve `merge_histogram_buckets` with `method="limit_buckets"` to compact buckets closer to the configured limit.
+
+issues: [49020]
+
+subtext:
+
+change_logs: [user]