diff --git a/changelog/8.9.0.asciidoc b/changelog/8.9.0.asciidoc new file mode 100644 index 00000000000..925387d79e7 --- /dev/null +++ b/changelog/8.9.0.asciidoc @@ -0,0 +1,79 @@ +// begin 8.9.0 relnotes + +[[release-notes-8.9.0]] +== 8.9.0 + +Review important information about the 8.9.0 release. + + + +[discrete] +[[breaking-changes-8.9.0]] +=== Breaking changes + +Breaking changes can prevent your application from optimal operation and +performance. Before you upgrade, review the breaking changes, then mitigate the +impact to your application. + +// TODO: add details and impact + +elastic-agent:: + +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/2890]] +.Status Command, Change Human Output To Be A Summary, Added Full Output. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/2890[#https://github.com/elastic/elastic-agent/pull/2890] +[%collapsible] +==== +status command has been changed, the default human output now uses a list format and summaries output. Full human output can be obtained with the new `full` option. +==== + + + + + +[discrete] +[[new-features-8.9.0]] +=== New features + +The 8.9.0 release adds the following new and notable features. + + +CLI:: + +* Add The Logs Subcommand To The Agent Cli. {CLI-pull}https://github.com/elastic/elastic-agent/pull/2745[#https://github.com/elastic/elastic-agent/pull/2745] {CLI-issue}https://github.com/elastic/elastic-agent/issues/114[#https://github.com/elastic/elastic-agent/issues/114] +elastic-agent:: + +* Allow Upgrade To Snapshots. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/2752[#https://github.com/elastic/elastic-agent/pull/2752] ++ +Allow upgrade to a specific snapshot version by specifying the build id + + +[discrete] +[[enhancements-8.9.0]] +=== Enhancements + + +Universal Profiling:: + +* Deployment/Kubernetes - Add Elements For Universal Profiling. {Universal Profiling-pull}https://github.com/elastic/elastic-agent/pull/2881[#https://github.com/elastic/elastic-agent/pull/2881] +elastic-agent:: + +* Lowercase Reported Hostnames Per Elastic Common Schema (Ecs) Guidelines For The Host.name Field. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/2767[#https://github.com/elastic/elastic-agent/pull/2767] + + + + +[discrete] +[[bug-fixes-8.9.0]] +=== Bug fixes + + +elastic-agent:: + +* Change Monitoring Socket. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3096[#https://github.com/elastic/elastic-agent/pull/3096] {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/2912[#https://github.com/elastic/elastic-agent/pull/2912] +* Fix Drop Processor For Monitoring Components. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/2982[#https://github.com/elastic/elastic-agent/pull/2982] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/2388[#https://github.com/elastic/elastic-agent/issues/2388] +synthetics:: + +* Bump Node To 18.16.0. {synthetics-pull}https://github.com/elastic/elastic-agent/pull/2696[#https://github.com/elastic/elastic-agent/pull/2696] + +// end 8.9.0 relnotes diff --git a/changelog/8.9.0.yaml b/changelog/8.9.0.yaml new file mode 100644 index 00000000000..abea4396607 --- /dev/null +++ b/changelog/8.9.0.yaml @@ -0,0 +1,93 @@ +version: 8.9.0 +entries: + - kind: bug-fix + summary: Bump node to 18.16.0 + description: "" + component: synthetics + pr: + - https://github.com/elastic/elastic-agent/pull/2696 + issue: [] + timestamp: 1684175757 + file: + name: 1684175757-bump-node-deps.yaml + checksum: 7539b8e2aa9f7fef1d1ea74874cd48b774193b6f + - kind: feature + summary: Allow upgrade to snapshots + description: Allow upgrade to a specific snapshot version by specifying the build id + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/2752 + issue: [] + timestamp: 1684731814 + file: + name: 1684731814-Allow-upgrade-to-snapshots.yaml + checksum: b60b174e5b776e82e5ad58921f316b9af8fce3c1 + - kind: feature + summary: Add the logs subcommand to the agent CLI + description: "" + component: CLI + pr: + - https://github.com/elastic/elastic-agent/pull/2745 + issue: + - https://github.com/elastic/elastic-agent/issues/114 + timestamp: 1685442237 + file: + name: 1685442237-add-logs-subcommand.yaml + checksum: 1ab375b6c055d8e4571c495fab96a88294971795 + - kind: enhancement + summary: Lowercase reported hostnames per Elastic Common Schema (ECS) guidelines for the host.name field. + description: Upgraded github.com/elastic/go-sysinfo from 1.10.0 to 1.11.0. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/2767 + issue: [] + timestamp: 1686142189 + file: + name: 1686142189-Lowercase-reported-hostnames-per-Elastic-Common-Schema-(ECS)-guidelines-for-the-host.name-field..yaml + checksum: e001fc5b954d119ea4e0875e42e15a574d64423b + - kind: enhancement + summary: deployment/kubernetes - add elements for Universal Profiling + description: "" + component: Universal Profiling + pr: + - https://github.com/elastic/elastic-agent/pull/2881 + issue: [] + timestamp: 1686845318 + file: + name: 1686845318-deployment-kubernetes-add-elements-for-Universal-Profiling.yaml + checksum: cf794c0ef5a74d8fc2ad78a5597979eacc7f46a0 + - kind: breaking-change + summary: status command, change human output to be a summary, added full output + description: status command has been changed, the default human output now uses a list format and summaries output. Full human output can be obtained with the new `full` option. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/2890 + issue: [] + timestamp: 1686949146 + file: + name: 1686949146-update-status-command.yaml + checksum: c8f2acfa356af46f991b9bda477e142ab3f3ce21 + - kind: bug-fix + summary: change monitoring socket + description: Change monitoring socket to use a hash of the id instead of the actual id. This shortens the path to be less than the 104 character limit. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3096 + - https://github.com/elastic/elastic-agent/pull/2912 + issue: [] + timestamp: 1687362147 + file: + name: 1687362147-change-monitoring-socket.yaml + checksum: 2e0a2d398075cde723ca95d7b4e8d44a53bd2439 + - kind: bug-fix + summary: Fix drop processor for monitoring components + description: It fixes the drop processor for monitoring component logs, instead of using the dataset that does not include any information about whether the component is a monitoring component it now uses the `component.id`. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/2982 + issue: + - https://github.com/elastic/elastic-agent/issues/2388 + timestamp: 1688401847 + file: + name: 1688401847-Fix-drop-processor-for-monitoring-components.yaml + checksum: 915711cf01de806c374675cbcad89d5f29b12254 diff --git a/changelog/fragments/1684175757-bump-node-deps.yaml b/changelog/fragments/1684175757-bump-node-deps.yaml deleted file mode 100644 index d507989143e..00000000000 --- a/changelog/fragments/1684175757-bump-node-deps.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Bump node to 18.16.0 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: synthetics - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1684731814-Allow-upgrade-to-snapshots.yaml b/changelog/fragments/1684731814-Allow-upgrade-to-snapshots.yaml deleted file mode 100644 index 632efbdbb3c..00000000000 --- a/changelog/fragments/1684731814-Allow-upgrade-to-snapshots.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Allow upgrade to snapshots - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: Allow upgrade to a specific snapshot version by specifying the build id -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1685442237-add-logs-subcommand.yaml b/changelog/fragments/1685442237-add-logs-subcommand.yaml deleted file mode 100644 index 82956bb53b7..00000000000 --- a/changelog/fragments/1685442237-add-logs-subcommand.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: feature -summary: Add the logs subcommand to the agent CLI -component: CLI -pr: https://github.com/elastic/elastic-agent/pull/2745 -issue: https://github.com/elastic/elastic-agent/issues/114 diff --git a/changelog/fragments/1686142189-Lowercase-reported-hostnames-per-Elastic-Common-Schema-(ECS)-guidelines-for-the-host.name-field..yaml b/changelog/fragments/1686142189-Lowercase-reported-hostnames-per-Elastic-Common-Schema-(ECS)-guidelines-for-the-host.name-field..yaml deleted file mode 100644 index 0bd8e8da4c8..00000000000 --- a/changelog/fragments/1686142189-Lowercase-reported-hostnames-per-Elastic-Common-Schema-(ECS)-guidelines-for-the-host.name-field..yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Lowercase reported hostnames per Elastic Common Schema (ECS) guidelines for the host.name field. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: Upgraded github.com/elastic/go-sysinfo from 1.10.0 to 1.11.0. - -# Affected component; a word indicating the component this changeset affects. -component: Elastic Agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/2767 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1686684090-Increase-Go-version-to-1.19.10..yaml b/changelog/fragments/1686684090-Increase-Go-version-to-1.19.10..yaml deleted file mode 100644 index c3e12afe668..00000000000 --- a/changelog/fragments/1686684090-Increase-Go-version-to-1.19.10..yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: security - -# Change summary; a 80ish characters long description of the change. -summary: Increase Go version to 1.19.10. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/2846 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1686770028-spec-timeout-units.yaml b/changelog/fragments/1686770028-spec-timeout-units.yaml deleted file mode 100644 index a33b364b44b..00000000000 --- a/changelog/fragments/1686770028-spec-timeout-units.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Explicitly specify timeout units as seconds in Endpoint spec file - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/2870 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/2863 diff --git a/changelog/fragments/1686833548-service-runtime-info-logging.yaml b/changelog/fragments/1686833548-service-runtime-info-logging.yaml deleted file mode 100644 index 46168c7ce2f..00000000000 --- a/changelog/fragments/1686833548-service-runtime-info-logging.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Log start and stop operations from service runtime at INFO level - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/2879 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/2864 diff --git a/changelog/fragments/1686845318-deployment-kubernetes-add-elements-for-Universal-Profiling.yaml b/changelog/fragments/1686845318-deployment-kubernetes-add-elements-for-Universal-Profiling.yaml deleted file mode 100644 index 8031710a954..00000000000 --- a/changelog/fragments/1686845318-deployment-kubernetes-add-elements-for-Universal-Profiling.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: deployment/kubernetes - add elements for Universal Profiling - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: Universal Profiling - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1686949146-update-status-command.yaml b/changelog/fragments/1686949146-update-status-command.yaml deleted file mode 100644 index eae6464c9ae..00000000000 --- a/changelog/fragments/1686949146-update-status-command.yaml +++ /dev/null @@ -1,34 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: status command, change human output to be a summary, added full output - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: >- - status command has been changed, the default human output now uses a list format - and summaries output. Full human output can be obtained with the new `full` option. - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1687251084-Fixed-diagnostics-logging-collection-on-k8s.yaml b/changelog/fragments/1687251084-Fixed-diagnostics-logging-collection-on-k8s.yaml deleted file mode 100644 index 4ed12601222..00000000000 --- a/changelog/fragments/1687251084-Fixed-diagnostics-logging-collection-on-k8s.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug - -# Change summary; a 80ish characters long description of the change. -summary: Fixed diagnostics logging collection on k8s - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: 2905 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 2899 diff --git a/changelog/fragments/1687362147-change-monitoring-socket.yaml b/changelog/fragments/1687362147-change-monitoring-socket.yaml deleted file mode 100644 index 98cfa7b97fe..00000000000 --- a/changelog/fragments/1687362147-change-monitoring-socket.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: change monitoring socket - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: Change monitoring socket to use a hash of the id instead of the actual id. This shortens the path to be less than the 104 character limit. - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1688401847-Fix-drop-processor-for-monitoring-components.yaml b/changelog/fragments/1688401847-Fix-drop-processor-for-monitoring-components.yaml deleted file mode 100644 index 38e90b0324c..00000000000 --- a/changelog/fragments/1688401847-Fix-drop-processor-for-monitoring-components.yaml +++ /dev/null @@ -1,13 +0,0 @@ -kind: bug-fix - -summary: Fix drop processor for monitoring components -description: >- - It fixes the drop processor for monitoring component logs, instead - of using the dataset that does not include any information about - whether the component is a monitoring component it now uses the - `component.id`. -component: elastic-agent - -pr: https://github.com/elastic/elastic-agent/pull/2982 - -issue: https://github.com/elastic/elastic-agent/issues/2388