Merge branch 'main' into fix/mongodbatlas-default-transport

open-telemetry · Dec 29, 2024 · a44f4ff · a44f4ff
2 parents 9b027df + b53b5ad
commit a44f4ff
Show file tree

Hide file tree

Showing 1,033 changed files with 38,023 additions and 29,296 deletions.
diff --git a/.chloggen/add_doris_to_build.yaml b/.chloggen/add_doris_to_build.yaml
diff --git a/...ms_escaped-quotes-in-keyvalue-parser.yaml → ...gen/azure-eventhub-observedtime-logs.yaml b/...ms_escaped-quotes-in-keyvalue-parser.yaml → ...gen/azure-eventhub-observedtime-logs.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: parseutils
+component: receiver/azureeventhub
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Handle escaped quotes when parsing pairs using SplitString.
+note: Ensure that observed timestamp is set when unmarshaling logs.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36176]
+issues: [36861]
 
 # (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.

diff --git a/...ticsearchexporter_merge-geo-location.yaml → ...ontexts-to-support-path-with-context.yaml b/...ticsearchexporter_merge-geo-location.yaml → ...ontexts-to-support-path-with-context.yaml
@@ -4,18 +4,18 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: elasticsearchexporter
+component: pkg/ottl
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Map *.geo.location.{lat,lon} as geo_point field in OTel mode
+note: "Change OTTL contexts to properly handle `ottl.Path` with context"
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36565]
+issues: [29017]
 
 # (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: In OTel mapping mode, merge *.geo.location.{lat,lon} to *.geo.location such that they are stored as geo_point in Elasticsearch.
+subtext: "The OTTL contexts have a new option `EnablePathContextNames` to enable support for expressing a statement's context via path names in the statement"
 
 # 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.
@@ -24,4 +24,4 @@ subtext: In OTel mapping mode, merge *.geo.location.{lat,lon} to *.geo.location
 # 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]
+change_logs: [api]
diff --git a/.chloggen/dd-conn-peer-tags.yaml b/.chloggen/dd-conn-peer-tags.yaml
diff --git a/.chloggen/dd-exp-peer-tags.yaml b/.chloggen/dd-exp-peer-tags.yaml
diff --git a/.chloggen/deprecate-routing-processor.yaml b/.chloggen/deprecate-routing-processor.yaml
diff --git a/.chloggen/kineticaexporter-unmaintained.yaml → .chloggen/deprecate_sapmexporter.yaml b/.chloggen/kineticaexporter-unmaintained.yaml → .chloggen/deprecate_sapmexporter.yaml
@@ -4,18 +4,27 @@
 change_type: deprecation
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: kineticaexporter
+component: sapmexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The kineticaexporter is now Unmaintained as it has no active code owners from the vendor
+note: Deprecate SAPM exporter
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36808]
+issues: [36028]
 
 # (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: |
+  The SAPM exporter is being marked as deprecated. Please use the `otlphttp` exporter with the configuration shown
+  below. Also update your pipeline configuration for Traces accordingly.
+  ```yaml
+    exporters:
+        otlphttp:
+            traces_endpoint: "${SPLUNK_INGEST_URL}/v2/trace/otlp"
+            headers:
+                "X-SF-Token": "${SPLUNK_ACCESS_TOKEN}"
+    ```
 
 # 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.

diff --git a/.chloggen/exporter_prometheusremotewriteexporter_exemplar-int.yaml b/.chloggen/exporter_prometheusremotewriteexporter_exemplar-int.yaml
diff --git a/...ggen/googlecloud-monitoring-receiver.yaml → ..._supervisor-reports-error-nop-config.yaml b/...ggen/googlecloud-monitoring-receiver.yaml → ..._supervisor-reports-error-nop-config.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: googlecloudmonitoringreceiver
+component: opampsupervisor
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix "no validation found" error if workload is running on Google Cloud Platform
+note: Report an 'Applied' remote config status when an empty config is received.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36607]
+issues: [36682]
 
 # (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.

diff --git a/.chloggen/gh-trace-skeleton.yaml b/.chloggen/gh-trace-skeleton.yaml
diff --git a/.chloggen/iss-35092.yaml b/.chloggen/iss-35092.yaml
diff --git a/.chloggen/k8sattributes-k8s-client-init-log.yaml b/.chloggen/k8sattributes-k8s-client-init-log.yaml
diff --git a/.chloggen/dd-config-api-key-fix.yaml → .chloggen/k8sobjects-data-structure.yaml b/.chloggen/dd-config-api-key-fix.yaml → .chloggen/k8sobjects-data-structure.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: connector/datadog, exporter/datadog, pkg/datadog
+component: k8sobjectsreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: throw error if datadog API key contains invalid characters
+note: ensure the `k8s.namespace.name` attribute is set for objects retrieved using the `watch` mode
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [36509]
+issues: [36352]
 
 # (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.
@@ -24,4 +24,4 @@ subtext:
 # 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]
+change_logs: []
diff --git a/.chloggen/kafka-exporter-aws-iam-oauth-bearer.yaml b/.chloggen/kafka-exporter-aws-iam-oauth-bearer.yaml