Merge remote-tracking branch 'upstream/main'

.chloggen/TEMPLATE.yaml

@@ -1,6 +1,4 @@
 # Use this changelog template to create an entry for release notes.
-# If your change doesn't affect end users, such as a test fix or a tooling change,
-# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
 change_type:
@@ -18,3 +16,12 @@ issues: []
 # 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/strict-dedup.yaml → .chloggen/add-ssh-endpoint-resource-attribute.yaml

@@ -6,13 +6,13 @@
 change_type: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: filelogreceiver
+component: receiver/sshcheck
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix issue where files were deduplicated unnecessarily
+note: Add the SSH endpoint as a resource attribute
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [24235]
+issues: [24441]
 
 # (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/userid.yaml → .chloggen/add_managed_identity_azuredataexplorer.yaml

@@ -2,13 +2,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: azuremonitorexporter
+component: azuredataexplorerexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Map enduser.id to Azure UserID tag
+note: Add support for managed identity. This enables users to not use Key based authentication
 
 # One or more tracking issues related to the change
-issues: [18103]
+issues: [21924]
 
 # (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/k8s-cluster-receiver-replicationcontroller.yaml → .chloggen/chloggen-config.yaml

@@ -1,20 +1,27 @@
 # Use this changelog template to create an entry for release notes.
-# If your change doesn't affect end users, such as a test fix or a tooling change,
-# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
 
 # 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: k8sclusterreceiver
+component: changelog
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Update k8s.replicationcontroller metrics to use mdatagen"
+note: Generate separate changelogs for end users and package consumers
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [10553]
+issues: [24014]
 
 # (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: [api]

.chloggen/mdatagen-resource-builder.yaml → .chloggen/collectdreceiver-migrate-from-opensus-to-pdata.yaml

@@ -6,10 +6,10 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: cmd/mdatagen
+component: receiver/collectdreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Introduce resource builder helper.
+note: Migrate from opencensus to pdata, change collectd, test to match pdata format.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [24360]
+issues: [20760]

.chloggen/config.yaml

@@ -0,0 +1,24 @@
+# The directory that stores individual changelog entries.
+# Each entry is stored in a dedicated yaml file.
+# - 'chloggen new' will copy the 'template_yaml' to this directory as a new entry file.
+# - 'chloggen validate' will validate that all entry files are valid.
+# - 'chloggen update' will read and delete all entry files in this directory, and update 'changelog_md'.
+# Specify as relative path from root of repo.
+# (Optional) Default: .chloggen
+entries_dir: .chloggen
+
+# This file is used as the input for individual changelog entries.
+# Specify as relative path from root of repo.
+# (Optional) Default: .chloggen/TEMPLATE.yaml
+template_yaml: .chloggen/TEMPLATE.yaml
+
+# The CHANGELOG file or files to which 'chloggen update' will write new entries
+# (Optional) Default filename: CHANGELOG.md
+change_logs:
+  user: CHANGELOG.md
+  api: CHANGELOG-API.md
+
+# The default change_log or change_logs to which an entry should be added.
+# If 'change_logs' is specified in this file, and no value is specified for 'default_change_logs',
+# then 'change_logs' MUST be specified in every entry file.
+default_change_logs: [user]

.chloggen/feat_boolean-time.yaml → .chloggen/dataset-exporter-make-shutdown-timeout-configurable.yaml

@@ -6,13 +6,13 @@
 change_type: 'enhancement'
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: 'pkg/ottl'
+component: datasetexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: 'Adds support for using boolean expressions with time objects'
+note: "Make duration of shutdown procedure configurable to minimise data losses."
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [22008]
+issues: [24415]
 
 # (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/feat_duration-func.yaml → .chloggen/dataset-exporter-populate-serverhost-field.yaml

@@ -6,13 +6,13 @@
 change_type: 'enhancement'
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: 'pkg/ottl'
+component: datasetexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Add new `Duration` converter to convert string to a Golang time.duration"
+note: "Make sure serverHost field is correctly and always populated on the DataSet events. For more information and available configuration options, please refer to the plugin readme file."
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [22015]
+issues: [20660, 24415]
 
 # (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/jgm-influxdbexporter-payload-limits.yaml → .chloggen/dd-receiver-span-id.yaml

@@ -6,13 +6,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: influxdbexporter
+component: datadogreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: limit size of write payload
+note: "add datadog trace and span id"
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [24001]
+issues: [23057]
 
 # (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/feat_boolean-duration.yaml → .chloggen/feat_math-time-duration.yaml

@@ -9,10 +9,10 @@ change_type: 'enhancement'
 component: 'pkg/ottl'
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: 'Adds support for using boolean expressions with durations'
+note: 'Add support for using addition and subtraction with time and duration'
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [22713]
+issues: [22009]
 
 # (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.