diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md index 9acd384693..8ae2a98569 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md @@ -51,7 +51,7 @@ Before starting the upgrade process, check which of the following recommendation * We strongly recommend that you routinely update your ECE installation to the most current version so that any bugs and security issues are fixed promptly. If you need to upgrade but are currently experiencing any issues with your platform, note that as long as ZooKeeper is running and healthy you should be able to upgrade (you can use the [get runners API](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-get-runners) to easily verify the health of the runners on the [ECE allocators](../../../deploy-manage/deploy/cloud-enterprise/ece-architecture.md#ece-architecture-allocators)). That is, healthy system deployments are not required in order to perform an upgrade successfully. -* Before upgrading to Elastic Cloud Enterprise 4.0, refer to the [lists of removals](/release-notes/breaking-changes/index.md) to find out about features and API endpoints that are no longer supported. +* Before upgrading to Elastic Cloud Enterprise 4.0, refer to the [lists of removals](cloud://release-notes/cloud-enterprise/breaking-changes.md) to find out about features and API endpoints that are no longer supported. * We strongly recommend that you do not attempt to perform certain actions during the upgrade process, such as: * Creating or changing Elasticsearch clusters and Kibana instances diff --git a/docset.yml b/docset.yml index 358d58bd52..cfcc0cd22d 100644 --- a/docset.yml +++ b/docset.yml @@ -384,10 +384,16 @@ subs: multi-arg-ref: "†footnoteref:[multi-arg]" yes-icon: "image:https://doc-icons.s3.us-east-2.amazonaws.com/icon-yes.png[Yes,20,15]" no-icon: "image:https://doc-icons.s3.us-east-2.amazonaws.com/icon-no.png[No,20,15]" + agent-repo: "https://github.com/elastic/elastic-agent/" + agent-issue: "https://github.com/elastic/elastic-agent/issues/" + agent-pull: "https://github.com/elastic/elastic-agent/pull/" es-repo: "https://github.com/elastic/elasticsearch/" es-issue: "https://github.com/elastic/elasticsearch/issues/" es-pull: "https://github.com/elastic/elasticsearch/pull/" es-commit: "https://github.com/elastic/elasticsearch/commit/" + fleet-server-repo: "https://github.com/elastic/fleet-server/" + fleet-server-issue: "https://github.com/elastic/fleet-server/issues/" + fleet-server-pull: "https://github.com/elastic/fleet-server/pull/" kib-repo: "https://github.com/elastic/kibana/" kib-issue: "https://github.com/elastic/kibana/issues/" kibana-issue: "'{kib-repo}issues/'" diff --git a/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md b/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md index 6cc5f3fae8..e12aafd984 100644 --- a/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md +++ b/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md @@ -20,7 +20,7 @@ Upgrading from a release candidate build, such as 8.0.0-rc1 or 8.0.0-rc2, is not * [{{es}} migration guide](elasticsearch://release-notes/breaking-changes.md) * [{{elastic-sec}} release notes](https://www.elastic.co/guide/en/security/current/release-notes.html) * [{{ents}} release notes](https://www.elastic.co/guide/en/enterprise-search/current/changelog.html) - * [{{fleet}} and {{agent}} release notes](/release-notes/fleet-elastic-agent.md) + * [{{fleet}} and {{agent}} release notes](/release-notes/fleet-elastic-agent/release-notes.md) * [{{kib}} release notes](kibana://release-notes/index.md) * [{{ls}} breaking changes](logstash://release-notes/breaking-changes.md) diff --git a/release-notes/breaking-changes/elastic-observability.md b/release-notes/breaking-changes/elastic-observability.md deleted file mode 100644 index 602f146703..0000000000 --- a/release-notes/breaking-changes/elastic-observability.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -navigation_title: "Elastic Observability" ---- - -# Elastic {{observability}} breaking changes [elastic-observability-breaking-changes] -Before you upgrade, carefully review the Elastic {{observability}} breaking changes and take the necessary steps to mitigate any issues. - -To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). - -% ## Next version [elastic-observability-nextversion-breaking-changes] -% **Release date:** Month day, year - -% ::::{dropdown} Title of breaking change -% Description of the breaking change. -% For more information, check [PR #](PR link). -% **Impact**
Impact of the breaking change. -% **Action**
Steps for mitigating deprecation impact. -% :::: - -% ## 9.0.0 [elastic-observability-900-breaking-changes] -% **Release date:** April 1, 2025 - -% ::::{dropdown} Title of breaking change -% Description of the breaking change. -% For more information, check [PR #](PR link). -% **Impact**
Impact of the breaking change. -% **Action**
Steps for mitigating deprecation impact. -% :::: \ No newline at end of file diff --git a/release-notes/breaking-changes/fleet-elastic-agent.md b/release-notes/breaking-changes/fleet-elastic-agent.md deleted file mode 100644 index 78b690653e..0000000000 --- a/release-notes/breaking-changes/fleet-elastic-agent.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -navigation_title: "Fleet and Elastic Agent" ---- - -# {{fleet}} and {{agent}} breaking changes [fleet-elastic-agent-breaking-changes] -Before you upgrade, carefully review the {{fleet}} and {{agent}} breaking changes and take the necessary steps to mitigate any issues. - -To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). - -% ## Next version [fleet-elastic-agent-nextversion-breaking-changes] -% **Release date:** Month day, year - -% ::::{dropdown} Title of breaking change -% Description of the breaking change. -% For more information, check [PR #](PR link). -% **Impact**
Impact of the breaking change. -% **Action**
Steps for mitigating deprecation impact. -% :::: - -% ## 9.0.0 [fleet-elastic-agent-900-breaking-changes] -% **Release date:** April 1, 2025 - -% ::::{dropdown} Title of breaking change -% Description of the breaking change. -% For more information, check [PR #](PR link). -% **Impact**
Impact of the breaking change. -% **Action**
Steps for mitigating deprecation impact. -% :::: \ No newline at end of file diff --git a/release-notes/breaking-changes/index.md b/release-notes/breaking-changes/index.md deleted file mode 100644 index 2e21de3288..0000000000 --- a/release-notes/breaking-changes/index.md +++ /dev/null @@ -1,5 +0,0 @@ -# Breaking changes [elastic-breaking-changes] - -Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the breaking changes for your Elastic version and take the necessary steps to mitigate any issues. - -To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). \ No newline at end of file diff --git a/release-notes/deprecations/elastic-security.md b/release-notes/deprecations/elastic-security.md deleted file mode 100644 index dad6dd6ed2..0000000000 --- a/release-notes/deprecations/elastic-security.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -navigation_title: "Elastic Security" ---- - -# {{elastic-sec}} deprecations [elastic-security-deprecations] -Review the deprecated functionality for your {{elastic-sec}} version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. - -To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). - -% ## Next version -% **Release date:** Month day, year - -% ::::{dropdown} Deprecation title -% Description of the deprecation. -% For more information, check [PR #](PR link). -% **Impact**
Impact of deprecation. -% **Action**
Steps for mitigating deprecation impact. -% :::: - -% ## 9.0.0 [elastic-security-900-deprecations] -% **Release date:** April 1, 2025 - -% ::::{dropdown} Deprecation title -% Description of the deprecation. -% For more information, check [PR #](PR link). -% **Impact**
Impact of deprecation. -% **Action**
Steps for mitigating deprecation impact. -% :::: \ No newline at end of file diff --git a/release-notes/deprecations/index.md b/release-notes/deprecations/index.md deleted file mode 100644 index 49b3109ffa..0000000000 --- a/release-notes/deprecations/index.md +++ /dev/null @@ -1,7 +0,0 @@ -# Deprecations [elastic-deprecations] -Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. - -Review the deprecated functionality for your Elastic version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. - -To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). - diff --git a/release-notes/breaking-changes/elastic-apm.md b/release-notes/elastic-apm/breaking-changes.md similarity index 83% rename from release-notes/breaking-changes/elastic-apm.md rename to release-notes/elastic-apm/breaking-changes.md index 7a376a24c5..90a951f34c 100644 --- a/release-notes/breaking-changes/elastic-apm.md +++ b/release-notes/elastic-apm/breaking-changes.md @@ -3,7 +3,7 @@ navigation_title: "Elastic APM" --- # Elastic APM breaking changes [elastic-apm-breaking-changes] -Before you upgrade, carefully review the Elastic APM breaking changes and take the necessary steps to mitigate any issues. +Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the Elastic APM breaking changes and take the necessary steps to mitigate any issues. To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). @@ -18,7 +18,7 @@ To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). % :::: ## 9.0.0 [elastic-apm-9-0-0-breaking-changes] -**Release date:** April 1, 2025 +**Release date:** April 2, 2025 % ::::{dropdown} Title of breaking change % Description of the breaking change. diff --git a/release-notes/deprecations/elastic-apm.md b/release-notes/elastic-apm/deprecations.md similarity index 62% rename from release-notes/deprecations/elastic-apm.md rename to release-notes/elastic-apm/deprecations.md index 5f26e831bc..1862aa11ba 100644 --- a/release-notes/deprecations/elastic-apm.md +++ b/release-notes/elastic-apm/deprecations.md @@ -3,7 +3,9 @@ navigation_title: "Elastic APM" --- # Elastic APM deprecations [elastic-apm-deprecations] -Review the deprecated functionality for your Elastic APM version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. +Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. + +Review the deprecated functionality for Elastic APM. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). @@ -18,7 +20,7 @@ To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). % :::: % ## 9.0.0 [elastic-apm-900-deprecations] -% **Release date:** April 1, 2025 +% **Release date:** April 2, 2025 % ::::{dropdown} Deprecation title % Description of the deprecation. diff --git a/release-notes/known-issues/elastic-apm.md b/release-notes/elastic-apm/known-issues.md similarity index 99% rename from release-notes/known-issues/elastic-apm.md rename to release-notes/elastic-apm/known-issues.md index a625c1be86..553b687767 100644 --- a/release-notes/known-issues/elastic-apm.md +++ b/release-notes/elastic-apm/known-issues.md @@ -6,7 +6,7 @@ navigation_title: "Elastic APM" --- # Elastic APM known issues [elastic-apm-known-issues] -Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Reviewing known issues can help you make informed decisions, such as upgrading to a new version. +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the Elastic APM known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. diff --git a/release-notes/elastic-apm.md b/release-notes/elastic-apm/release-notes.md similarity index 100% rename from release-notes/elastic-apm.md rename to release-notes/elastic-apm/release-notes.md diff --git a/release-notes/elastic-apm/toc.yml b/release-notes/elastic-apm/toc.yml new file mode 100644 index 0000000000..f1433648e4 --- /dev/null +++ b/release-notes/elastic-apm/toc.yml @@ -0,0 +1,6 @@ +toc: + - file: release-notes.md + children: + - file: known-issues.md + - file: breaking-changes.md + - file: deprecations.md \ No newline at end of file diff --git a/release-notes/elastic-cloud-serverless.md b/release-notes/elastic-cloud-serverless/changelog.md similarity index 100% rename from release-notes/elastic-cloud-serverless.md rename to release-notes/elastic-cloud-serverless/changelog.md diff --git a/release-notes/deprecations/elastic-cloud-serverless.md b/release-notes/elastic-cloud-serverless/deprecations.md similarity index 100% rename from release-notes/deprecations/elastic-cloud-serverless.md rename to release-notes/elastic-cloud-serverless/deprecations.md diff --git a/release-notes/known-issues/elastic-cloud-serverless.md b/release-notes/elastic-cloud-serverless/known-issues.md similarity index 79% rename from release-notes/known-issues/elastic-cloud-serverless.md rename to release-notes/elastic-cloud-serverless/known-issues.md index 3275f6d62f..6ba62f1612 100644 --- a/release-notes/known-issues/elastic-cloud-serverless.md +++ b/release-notes/elastic-cloud-serverless/known-issues.md @@ -2,7 +2,7 @@ navigation_title: "Elastic Cloud Serverless" --- # {{serverless-full}} known issues [elastic-cloud-serverless-known-issues] -Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Reviewing known issues can help you make informed decisions. +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the {{serverless-full}} known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. diff --git a/release-notes/elastic-cloud-serverless/toc.yml b/release-notes/elastic-cloud-serverless/toc.yml new file mode 100644 index 0000000000..37032c6bd7 --- /dev/null +++ b/release-notes/elastic-cloud-serverless/toc.yml @@ -0,0 +1,5 @@ +toc: + - file: changelog.md + children: + - file: known-issues.md + - file: deprecations.md \ No newline at end of file diff --git a/release-notes/elastic-observability/breaking-changes.md b/release-notes/elastic-observability/breaking-changes.md new file mode 100644 index 0000000000..2152563328 --- /dev/null +++ b/release-notes/elastic-observability/breaking-changes.md @@ -0,0 +1,51 @@ +--- +navigation_title: "Elastic Observability" +--- + +# Elastic {{observability}} breaking changes [elastic-observability-breaking-changes] +Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the Elastic {{observability}} breaking changes and take the necessary steps to mitigate any issues. + +To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). + +% ## Next version [elastic-observability-nextversion-breaking-changes] +% **Release date:** Month day, year + +% ::::{dropdown} Title of breaking change +% Description of the breaking change. +% For more information, check [PR #](PR link). +% **Impact**
Impact of the breaking change. +% **Action**
Steps for mitigating deprecation impact. +% :::: + +% ## 9.0.0 [elastic-observability-900-breaking-changes] +% **Release date:** April 2, 2025 + +::::{dropdown} Profiling now defaults to 19Hz sampling frequency +For more information, check ({{kibana-pull}}202278[#202278]). +:::: + +::::{dropdown} Removed log stream and settings pages +The following have been removed: +* Logs Stream +* Logs settings page +* Logs stream panel in Dashboards + +For more information, check ({{kibana-pull}}203996[#203996]). + +**Action** +To explore your logs, use the contextual experience in Discover. + +To view log streams, use Discover sessions. + + +:::: + +::::{dropdown} Removed Logs Explorer +Logs Explorer has been removed. + + +For more information, refer to ({kibana-pull}203685[#203685]). + +**Action** +Use the improved logs exploration experience in Discover. +:::: \ No newline at end of file diff --git a/release-notes/deprecations/elastic-observability.md b/release-notes/elastic-observability/deprecations.md similarity index 63% rename from release-notes/deprecations/elastic-observability.md rename to release-notes/elastic-observability/deprecations.md index a9043f71f7..9e6827f980 100644 --- a/release-notes/deprecations/elastic-observability.md +++ b/release-notes/elastic-observability/deprecations.md @@ -3,7 +3,9 @@ navigation_title: "Elastic Observability" --- # Elastic {{observability}} deprecations [elastic-observability-deprecations] -Review the deprecated functionality for your Elastic {{observability}} version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. +Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. + +Review the deprecated functionality for Elastic {{observability}}. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). @@ -18,7 +20,7 @@ To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). % :::: % ## 9.0.0 [elastic-observability-900-deprecations] -% **Release date:** April 1, 2025 +% **Release date:** April 2, 2025 % ::::{dropdown} Deprecation title % Description of the deprecation. diff --git a/release-notes/known-issues/elastic-observability.md b/release-notes/elastic-observability/known-issues.md similarity index 79% rename from release-notes/known-issues/elastic-observability.md rename to release-notes/elastic-observability/known-issues.md index 835d001969..4d8c2acef7 100644 --- a/release-notes/known-issues/elastic-observability.md +++ b/release-notes/elastic-observability/known-issues.md @@ -3,7 +3,7 @@ navigation_title: "Elastic Observability" --- # Elastic {{observability}} known issues [elastic-observability-known-issues] -Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Reviewing known issues can help you make informed decisions, such as upgrading to a new version. +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the Elastic {{observability}} known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. diff --git a/release-notes/elastic-observability.md b/release-notes/elastic-observability/release-notes.md similarity index 70% rename from release-notes/elastic-observability.md rename to release-notes/elastic-observability/release-notes.md index c9e53811ed..db4de57546 100644 --- a/release-notes/elastic-observability.md +++ b/release-notes/elastic-observability/release-notes.md @@ -19,8 +19,8 @@ To check for security updates, go to [Security announcements for the Elastic sta % * ## 9.0.0 [elastic-observability-900-release-notes] -**Release date:** April 1, 2025 +**Release date:** April 2, 2025 -### Features and enhancements [elastic-observability-900-features-enhancements] - -### Fixes [elastic-observability-900-fixes] \ No newline at end of file +### Fixes [elastic-observability-900-fixes] +* Fixes chat on the Alerts page ({{kibana-pull}}197126[#197126]) +* Fixes an error that could prevent the Observability Infrastructure Inventory view from loading after an upgrade due to missing versioning on inventory_view_saved_object ({{kibana-pull}}207007[#207007]) \ No newline at end of file diff --git a/release-notes/elastic-observability/toc.yml b/release-notes/elastic-observability/toc.yml new file mode 100644 index 0000000000..f1433648e4 --- /dev/null +++ b/release-notes/elastic-observability/toc.yml @@ -0,0 +1,6 @@ +toc: + - file: release-notes.md + children: + - file: known-issues.md + - file: breaking-changes.md + - file: deprecations.md \ No newline at end of file diff --git a/release-notes/elastic-security.md b/release-notes/elastic-security.md deleted file mode 100644 index 2ab28c1459..0000000000 --- a/release-notes/elastic-security.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -navigation_title: "Elastic Security" -mapped_pages: - - https://www.elastic.co/guide/en/security/master/release-notes-header-9.0.0.html - - https://www.elastic.co/guide/en/security/current/release-notes.html ---- -# {{elastic-sec}} release notes [elastic-security-release-notes] - -Review the changes, fixes, and more in each version of {{elastic-sec}}. - -To check for security updates, go to [Security announcements for the Elastic stack](https://discuss.elastic.co/c/announcements/security-announcements/31). - -% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections. - -% ## version.next [elastic-security-next-release-notes] -% **Release date:** Month day, year - -% ### Features and enhancements [elastic-security-next-features-enhancements] -% * - -% ### Fixes [elastic-security-next-fixes] -% * - -## 9.0.0 [elastic-security-900-release-notes] -**Release date:** April 1, 2025 - -### Features and enhancements [elastic-security-900-features-enhancements] - -### Fixes [elastic-security-900-fixes] diff --git a/release-notes/breaking-changes/elastic-security.md b/release-notes/elastic-security/breaking-changes.md similarity index 85% rename from release-notes/breaking-changes/elastic-security.md rename to release-notes/elastic-security/breaking-changes.md index 2d973f8b35..a210eedb75 100644 --- a/release-notes/breaking-changes/elastic-security.md +++ b/release-notes/elastic-security/breaking-changes.md @@ -1,9 +1,8 @@ --- navigation_title: "Elastic Security" --- - # {{elastic-sec}} breaking changes [elastic-security-breaking-changes] -Before you upgrade, carefully review the {{elastic-sec}} breaking changes and take the necessary steps to mitigate any issues. +Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the {{elastic-sec}} breaking changes and take the necessary steps to mitigate any issues. To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). @@ -18,7 +17,7 @@ To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). % :::: ## 9.0.0 [elastic-security-900-breaking-changes] -**Release date:** April 1, 2025 +**Release date:** April 2, 2025 ::::{dropdown} Removed legacy security rules bulk endpoints * `POST /api/detection_engine/rules/_bulk_create` has been replaced by `POST /api/detection_engine/rules/_import` @@ -68,4 +67,16 @@ Update your implementations to use the new endpoints: * Remove references to `GET /api/endpoint/action_log/{{agent_id}}` endpoint. * Remove references to `GET /api/endpoint/metadata/transforms` endpoint. * Replace references to deprecated endpoints with the replacements listed in the breaking change details. +:::: + +::::{dropdown} Refactors the Timeline HTTP API endpoints +For more information, check ({{kibana-pull}}200633[#200633]). +:::: + +::::{dropdown} Removes deprecated {{elastic-defend}} APIs +For more information, check ({{kibana-pull}}199598[#199598]). +:::: + +::::{dropdown} Removes deprecated API endpoints for bulk CRUD actions on detection rules +For more information, check ({{kibana-pull}}197422[#197422]) and ({{kibana-pull}}207906[#207906]). :::: \ No newline at end of file diff --git a/release-notes/elastic-security/deprecations.md b/release-notes/elastic-security/deprecations.md new file mode 100644 index 0000000000..193628843d --- /dev/null +++ b/release-notes/elastic-security/deprecations.md @@ -0,0 +1,43 @@ +--- +navigation_title: "Elastic Security" +--- + +# {{elastic-sec}} deprecations [elastic-security-deprecations] +Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. + +Review the deprecated functionality for {{elastic-sec}}. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. + +To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). + +% ## Next version +% **Release date:** Month day, year + +% ::::{dropdown} Deprecation title +% Description of the deprecation. +% For more information, check [PR #](PR link). +% **Impact**
Impact of deprecation. +% **Action**
Steps for mitigating deprecation impact. +% :::: + +% ## 9.0.0 [elastic-security-900-deprecations] +% **Release date:** April 2, 2025 + +::::{dropdown} Renames the `integration-assistant` plugin +Renames the `integration-assistant` plugin to `automatic-import` to match the associated feature. +For more information, check ({{kibana-pull}}207325[#207325]). +:::: + +::::{dropdown} Removes legacy risk engine +Removes all legacy risk engine code and features. +For more information, check ({{kibana-pull}}201810[#201810]). +:::: + +::::{dropdown} Removes {{elastic-defend}} API endoints +Removes deprecated API endpoints for {{elastic-defend}}. +For more information, check ({{kibana-pull}}199598[#199598]). +:::: + +::::{dropdown} Deprecates SIEM signals migration APIs +Deprecates the SIEM signals migration APIs. +For more information, check ({{kibana-pull}}202662[#202662]). +:::: \ No newline at end of file diff --git a/release-notes/known-issues/elastic-security.md b/release-notes/elastic-security/known-issues.md similarity index 69% rename from release-notes/known-issues/elastic-security.md rename to release-notes/elastic-security/known-issues.md index 2845244f73..6ad515548e 100644 --- a/release-notes/known-issues/elastic-security.md +++ b/release-notes/elastic-security/known-issues.md @@ -6,7 +6,7 @@ navigation_title: "Elastic Security" --- # {{elastic-sec}} known issues [elastic-security-known-issues] -Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Reviewing known issues can help you make informed decisions, such as upgrading to a new version. +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the {{elastic-sec}} known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. @@ -24,6 +24,10 @@ Known issues are significant defects or limitations that may impact your impleme **Elastic Stack versions: 9.0.0** On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. - ::: +:::{dropdown} Manually running custom query rules with suppression could suppress more alerts than expected +**Elastic Stack versions: 9.0.0** + +On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. +::: \ No newline at end of file diff --git a/release-notes/elastic-security/release-notes.md b/release-notes/elastic-security/release-notes.md new file mode 100644 index 0000000000..4809bd9df0 --- /dev/null +++ b/release-notes/elastic-security/release-notes.md @@ -0,0 +1,41 @@ +--- +navigation_title: "Elastic Security" +mapped_pages: + - https://www.elastic.co/guide/en/security/master/release-notes-header-9.0.0.html + - https://www.elastic.co/guide/en/security/current/release-notes.html +--- +# {{elastic-sec}} release notes [elastic-security-release-notes] + +Review the changes, fixes, and more in each version of {{elastic-sec}}. + +To check for security updates, go to [Security announcements for the Elastic stack](https://discuss.elastic.co/c/announcements/security-announcements/31). + +% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections. + +% ## version.next [elastic-security-next-release-notes] +% **Release date:** Month day, year + +% ### Features and enhancements [elastic-security-next-features-enhancements] +% * + +% ### Fixes [elastic-security-next-fixes] +% * + +## 9.0.0 [elastic-security-900-release-notes] +**Release date:** April 1, 2025 + +### Features and enhancements [elastic-security-900-features-enhancements] +* Enables Automatic Import to accept CEL log samples ({{kibana-pull}}206491[#206491]) +* Applies the latest Elastic UI framework (EUI) to {{elastic-sec}} features ({{kibana-pull}}204007[#204007]) and ({{kibana-pull}}204908[#204908]) +* Adds the option to view {es} queries that run during rule execution for threshold, custom query, and {{ml}} rules ({{kibana-pull}}203320[#203320]) +* Enables Automatic Import to accept CEL log samples ({{kibana-pull}}206491[#206491]) +* Applies the latest Elastic UI framework (EUI) to {{elastic-sec}} features ({{kibana-pull}}204007[#204007]) and ({{kibana-pull}}204908[#204908]) +* Adds the option to view {{es}} queries that run during rule execution for threshold, custom query, and {{ml}} rules ({{kibana-pull}}203320[#203320]) +* Enhances Automatic Import by including setup and troubleshooting documentation for each input type that's selected in the readme ({{kibana-pull}}206477[#206477]) +* Allows users to include `closed` alerts in risk score calculations ({{kibana-pull}}201909[#201909]) +* Adds the ability to continue to the Entity Analytics dashboard when there is no data ({{kibana-pull}}201363[#201363]) +* Modifies the privilege-checking behavior during rule execution. Now, only read privileges of extant indices are checked during rule execution ({{kibana-pull}}177658[#177658]) + +### Fixes [elastic-security-900-fixes] +* Ensures that table actions use standard colors ({{kibana-pull}}207743[#207743]) +* Fixes a bug with the **Save and continue** button on a {fleet} form ({{kibana-pull}}211563[#211563]) \ No newline at end of file diff --git a/release-notes/elastic-security/toc.yml b/release-notes/elastic-security/toc.yml new file mode 100644 index 0000000000..f1433648e4 --- /dev/null +++ b/release-notes/elastic-security/toc.yml @@ -0,0 +1,6 @@ +toc: + - file: release-notes.md + children: + - file: known-issues.md + - file: breaking-changes.md + - file: deprecations.md \ No newline at end of file diff --git a/release-notes/fleet-elastic-agent.md b/release-notes/fleet-elastic-agent.md deleted file mode 100644 index 0a19dfdd52..0000000000 --- a/release-notes/fleet-elastic-agent.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -navigation_title: "Fleet and Elastic Agent" -mapped_pages: - - https://www.elastic.co/guide/en/fleet/current/release-notes.html ---- - -# {{fleet}} and {{agent}} release notes [fleet-elastic-agent-release-notes] - -Review the changes, fixes, and more in each version of {{fleet}} and {{agent}}. - -To check for security updates, go to [Security announcements for the Elastic stack](https://discuss.elastic.co/c/announcements/security-announcements/31). - -{{agent}} integrates and manages {{beats}} for data collection, and Beats changes may impact {{agent}} functionality. To check for {{agent}} changes in {{beats}}, go to [{{beats}} release notes](asciidocalypse://docs/beats/docs/release-notes/index.md). - -% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections. -% For each new version section, include the Fleet and Elastic Agent and Kibana changes. - -% ## version.next [fleet-elastic-agent-next-release-notes] -% **Release date:** Month day, year - -% ### Features and enhancements [fleet-elastic-agent-next-features-enhancements] -% * - -% ### Fixes [fleet-elastic-agent-next-fixes] -% * - - -## 9.0.0 [fleet-elastic-agent-900-release-notes] -**Release date:** April 1, 2025 - -### Features and enhancements [fleet-elastic-agent-900-features-enhancements] - -### Fixes [fleet-elastic-agent-900-fixes] - - - - - diff --git a/release-notes/fleet-elastic-agent/breaking-changes.md b/release-notes/fleet-elastic-agent/breaking-changes.md new file mode 100644 index 0000000000..f7184a61ae --- /dev/null +++ b/release-notes/fleet-elastic-agent/breaking-changes.md @@ -0,0 +1,104 @@ +--- +navigation_title: "Fleet and Elastic Agent" +--- + +# {{fleet}} and {{agent}} breaking changes [fleet-elastic-agent-breaking-changes] +Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the {{fleet}} and {{agent}} breaking changes and take the necessary steps to mitigate any issues. + +To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). + +% ## Next version [fleet-elastic-agent-nextversion-breaking-changes] +% **Release date:** Month day, year + +% ::::{dropdown} Title of breaking change +% Description of the breaking change. +% For more information, check [PR #](PR link). +% **Impact**
Impact of the breaking change. +% **Action**
Steps for mitigating deprecation impact. +% :::: + +## 9.0.0 [fleet-elastic-agent-900-breaking-changes] +**Release date:** April 2, 2025 + +::::{dropdown} Removed deprecated `epm` Fleet APIs +Removed `GET/POST/DELETE /epm/packages/:pkgkey` APIs in favor of the `GET/POST/DELETE /epm/packages/:pkgName/:pkgVersion`. + +**Impact**
+* Removed `experimental` query parameter in `GET /epm/packages` and `GET /epm/categories` +* Removed `response` in response in `* /epm/packages*` and `GET /epm/categories` +* Removed `savedObject` in `/epm/packages` response in favor of `installationInfo` + +For more information, check ({{kibana-pull}}198434[#198434]). +:::: + +::::{dropdown} Removed deprecated Fleet APIs for agents endpoints +Removed the following API endpoints: + +* `POST /service-tokens` in favor of `POST /service_tokens` +* `GET /agent-status` in favor `GET /agent_status` +* `PUT /agents/:agentid/reassign` in favor of `POST /agents/:agentid/reassign` + +Removed deprecated parameters or responses: + +* Removed `total` from `GET /agent_status` response +* Removed `list` from `GET /agents` response + +For more information, check ({{kibana-pull}}198313[#198313]). +:::: + +::::{dropdown} Removed `cloud defend` support for {{agent}} +Support for `cloud-defend` (Defend for Containers) has been removed. The package has been removed from the {{agent}} packaging scripts and template Kubernetes files. + +For more information, check ({{agent-pull}}5481[#5481]). +:::: + +::::{dropdown} Removed `username` and `password` default values for {{agent}} +The default values for `username` and `password` have been removed for when {{agent}} is running in container mode. The {es} `api_key` can now be set in that mode using the `ELASTICSEARCH_API_KEY` environment variable. + +For more information, check ({{agent-pull}}5536[#5536]). +:::: + +::::{dropdown} Changed Ubuntu-based Docker images for {{agent}} +The default Ubuntu-based Docker images used for {{agent}} have been changed to UBI-minimal-based images, to reduce the overall footprint of the agent Docker images and to improve compliance with enterprise standards. + +For more information, check ({{agent-pull}}6427[#6427]). +:::: + +::::{dropdown} Removed `--path.install` flag declaration from {{agent}} `paths` command +The deprecated `--path.install` flag declaration has been removed from the {{agent}} `paths` command and its use removed from the `container` and `enroll` commands. + +For more information, check ({{agent-pull}}6461[#6461]) and ({{agent-pull}}2489[#2489]). +:::: + +::::{dropdown} Changed the default {{agent}} installation and upgrade +The default {{agent}} installation and ugprade have been changed to include only the `agentbeat`, `endpoint-security` and `pf-host-agent` components. Additional components can be included using flags. + +For more information, check ({{agent-pull}}6542[#6542]). +:::: + +::::{dropdown} Removed deprecated settings API endpoints in Fleet +* `GET/DELETE/POST enrollment-api-keys`: removed in favor of `GET/DELETE/POST enrollment_api_keys` +* Removed `list` property from `GET enrollment_api_keys` response in favor of `items` +* `GET/POST /settings`: `fleet_server_hosts` was removed from the response and body + +For more information, check ({{kibana-pull}}198799[#198799]). +:::: + +::::{dropdown} Removed deprecated settings API endpoints in Fleet +* `GET/DELETE/POST enrollment-api-keys`: removed in favor of `GET/DELETE/POST enrollment_api_keys` +* Removed `list` property from `GET enrollment_api_keys` response in favor of `items` +* `GET/POST /settings`: `fleet_server_hosts` was removed from the response and body + +For more information, check ({{kibana-pull}}198799[#198799]). +:::: + +::::{dropdown} Removed deprecated `topics` property for kafka output in favor of the `topic` property +Removed deprecated property `topics` from output APIs in response and requests (`(GET|POST|PUT) /api/fleet/outputs`) in favor of the `topic` property. +For more information, check ({{kibana-pull}}199226[#199226]). +:::: + +::::{dropdown} Limit pagination size to 100 when retrieving full policy or `withAgentCount` in Fleet +In addition to the new pagination limit size of 100, retrieving agent policies without agent count is now the new default behavior, and a new query parameter `withAgentCount` was added to retrieve the agent count. + +For more information, check ({{kibana-pull}}196887[#196887]). +:::: \ No newline at end of file diff --git a/release-notes/deprecations/fleet-elastic-agent.md b/release-notes/fleet-elastic-agent/deprecations.md similarity index 63% rename from release-notes/deprecations/fleet-elastic-agent.md rename to release-notes/fleet-elastic-agent/deprecations.md index 204103d594..4ef0ee64b1 100644 --- a/release-notes/deprecations/fleet-elastic-agent.md +++ b/release-notes/fleet-elastic-agent/deprecations.md @@ -3,7 +3,9 @@ navigation_title: "Fleet and Elastic Agent" --- # {{fleet}} and {{agent}} deprecations [fleet-elastic-agent-deprecations] -Review the deprecated functionality for your {{fleet}} and {{agent}} version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. +Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. + +Review the deprecated functionality for {{fleet}} and {{agent}}. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). @@ -18,7 +20,7 @@ To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md). % :::: % ## 9.0.0 [fleet-elastic-agent-900-deprecations] -% **Release date:** April 1, 2025 +% **Release date:** April 2, 2025 % ::::{dropdown} Deprecation title % Description of the deprecation. diff --git a/release-notes/known-issues/fleet-elastic-agent.md b/release-notes/fleet-elastic-agent/known-issues.md similarity index 79% rename from release-notes/known-issues/fleet-elastic-agent.md rename to release-notes/fleet-elastic-agent/known-issues.md index ff9b5ab0c0..dbe37b5720 100644 --- a/release-notes/known-issues/fleet-elastic-agent.md +++ b/release-notes/fleet-elastic-agent/known-issues.md @@ -3,7 +3,7 @@ navigation_title: "Fleet and Elastic Agent" --- # {{fleet}} and {{agent}} known issues [fleet-elastic-agent-known-issues] -Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Reviewing known issues can help you make informed decisions, such as upgrading to a new version. +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the {{fleet}} and {{agent}} known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. diff --git a/release-notes/fleet-elastic-agent/release-notes.md b/release-notes/fleet-elastic-agent/release-notes.md new file mode 100644 index 0000000000..b538f30cc3 --- /dev/null +++ b/release-notes/fleet-elastic-agent/release-notes.md @@ -0,0 +1,63 @@ +--- +navigation_title: "Fleet and Elastic Agent" +mapped_pages: + - https://www.elastic.co/guide/en/fleet/current/release-notes.html +--- + +# {{fleet}} and {{agent}} release notes [fleet-elastic-agent-release-notes] + +Review the changes, fixes, and more in each version of {{fleet}} and {{agent}}. + +To check for security updates, go to [Security announcements for the Elastic stack](https://discuss.elastic.co/c/announcements/security-announcements/31). + +{{agent}} integrates and manages {{beats}} for data collection, and Beats changes may impact {{agent}} functionality. To check for {{agent}} changes in {{beats}}, go to [{{beats}} release notes](asciidocalypse://docs/beats/docs/release-notes/index.md). + +% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections. +% For each new version section, include the Fleet and Elastic Agent and Kibana changes. + +% ## version.next [fleet-elastic-agent-next-release-notes] +% **Release date:** Month day, year + +% ### Features and enhancements [fleet-elastic-agent-next-features-enhancements] +% * + +% ### Fixes [fleet-elastic-agent-next-fixes] +% * + + +## 9.0.0 [fleet-elastic-agent-900-release-notes] +**Release date:** April 2, 2025 + +### Features and enhancements [fleet-elastic-agent-900-features-enhancements] +* New setting allowing automatic deletion of unenrolled agents in Fleet settings ({{kibana-pull}}195544[#195544]) +* Adds the Azure Asset Inventory definition to Cloudbeat for {{agent}} {{agent-pull}}5323[#5323] +* Adds Kubernetes deployment of the Elastic Distribution of OTel Collector named "gateway" to the Helm kube-stack deployment for {{agent}} {{agent-pull}}6444[#6444] +* Adds the filesource providert to composable inputs. The provider watches for changes of the files and updates the values of the variables when the content of the file changes for {{agent}} {{agent-pull}}6587[#6587] and {{agent-issue}}6362[#6362] +* Adds the jmxreceiver to the Elastic Distribution of OTel Collector for {{agent}} {{agent-pull}}6601[#6601] +* Adds support for context variables in outputs as well as a default provider prefix for {{agent}} {{agent-pull}}6602[#6602] and {{agent-issue}}6376[#6376] +* Adds the Nginx receiver and Redis receiver OTel components for {{agent}} {{agent-pull}}6627[#6627] +* Adds `--id` (`ELASTIC_AGENT_ID` environment variable for container) and `--replace-token` (`FLEET_REPLACE_TOKEN` environment variable for container) enrollment options for {{agent}} {{agent-pull}}6498[#6498] +* Updates Go version to 1.22.10 in {{agent}} {{agent-pull}}6236[#6236] +* Improves filtering and visibility of `Uninstalled` and `Orphaned` agents in {{fleet}}, by differentiating them from `Offline` agents {{kibana-pull}}205815[#205815] +* Introduces air-gapped configuration for bundled packages in {{fleet}} {{kibana-pull}}202435[#202435] +* Updates removed parameters of the {{fleet}} -> {{ls}} output configurations {{kibana-pull}}210115[#210115] +* Updates the maximum supported package version in {{fleet}} {{kibana-pull}}196675[#196675] +* Replaces the use of `context.TODO` and `context.Background` in logger function calls for most {{fleet-server}} use cases {{fleet-server-pull}}4168[#4168] {{fleet-server-issue}}3087[#3087] +* Refactor the {{fleet-server}} API constructor to use functional opts instead of a long list of pointers {{fleet-server-pull}}4169[#4169] {{fleet-server-issue}}3823[#3823] +* Removes the deprecated `policy_throttle` configuration setting in favour of the newer `policy-limit` for {{fleet-server}} {{fleet-server-pull}}4288[#4288] +* Adds the ability for {{agent}} to enroll using a specific ID {{fleet-server-pull}}4290[#4290] and {{fleet-server-issue}}4226[#4226] +* Adds the Filebeat receiver into {{agent}} {{agent-pull}}5833[#5833] +* Updates OTel components to v0.119.0 in {{agent}} {{agent-pull}}6713[#6713] +% * Removes old bundled.yaml from oas, fixed tags ({{kibana-pull}}194788[#194788]) + +### Fixes [fleet-elastic-agent-900-fixes] +* Fixes a validation error that occurs on multi-text input fields in {{fleet}} ({{kibana-pull}}205768[#205768]) +* Adds a context timeout to the bulker flush in {{fleet-server}} so it times out if it takes more time than the deadline {{fleet-server-pull}}3986[#3986] +* Removes a race condition that may occur when remote {es} outputs are used in {{fleet-server}} {{fleet-server-pull}}4171[#4171] +* Uses the `chi/middleware.Throttle` package to track in-flight requests and return a 429 response when the limit is reached in {{fleet-server}} {{fleet-server-pull}}4402[#4402] and {fleet-server-issue}4400[#4400] +* Fixes logical race conditions in the `kubernetes_secrets` provider in {{agent}} {{agent-pull}}6623[#6623] +* Resolves the proxy to inject into agent component configurations using the Go `http` package in {{agent}} {{agent-pull}}6675[#6675] and {{agent-issue}}6209[#6209] + + + + diff --git a/release-notes/fleet-elastic-agent/toc.yml b/release-notes/fleet-elastic-agent/toc.yml new file mode 100644 index 0000000000..f1433648e4 --- /dev/null +++ b/release-notes/fleet-elastic-agent/toc.yml @@ -0,0 +1,6 @@ +toc: + - file: release-notes.md + children: + - file: known-issues.md + - file: breaking-changes.md + - file: deprecations.md \ No newline at end of file diff --git a/release-notes/index.md b/release-notes/index.md index 50f7c443b4..302e853d91 100644 --- a/release-notes/index.md +++ b/release-notes/index.md @@ -2,11 +2,11 @@ Learn about the latest changes, issues, fixes, and deprecations for Elastic releases by reviewing the release notes. -For information about the latest changes to Elastic APIs, check the [APIs changelog](https://www.elastic.co/docs/api/changes). +For information about the latest changes to Elastic APIs, check [APIs changelog](https://www.elastic.co/docs/api/changes). We recommend you upgrade to the latest Elastic version. To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md). -Additional resources: +To learn more about Elastic releases, use the following resources: * Join the [Elastic community forums](https://discuss.elastic.co/) * Check out the [Elastic Blog](https://www.elastic.co/blog) * Reach out to [Elastic Support](https://mail.google.com/mail/u/0/?fs=1&tf=cm&source=mailto&to=support@elastic.co) diff --git a/release-notes/known-issues/index.md b/release-notes/known-issues/index.md deleted file mode 100644 index 39351c2f81..0000000000 --- a/release-notes/known-issues/index.md +++ /dev/null @@ -1,2 +0,0 @@ -# Known issues [elastic-known-issues] -Known issues are significant problems or defects that we are actively working on. Review known issues when making important decisions, such as upgrading to a new version. \ No newline at end of file diff --git a/release-notes/known-issues/search-ui.md b/release-notes/search-ui-known-issues.md similarity index 65% rename from release-notes/known-issues/search-ui.md rename to release-notes/search-ui-known-issues.md index 90e43f159e..bae33c7ab1 100644 --- a/release-notes/known-issues/search-ui.md +++ b/release-notes/search-ui-known-issues.md @@ -6,6 +6,7 @@ navigation_title: "Search" --- # Search known issues [search-known-issues] +Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the {{fleet}} and {{agent}} known issues to help you make informed decisions, such as upgrading to a new version. % Use the following template to add entries to this page. diff --git a/release-notes/toc.yml b/release-notes/toc.yml index 76f71e63bb..695e0a990d 100644 --- a/release-notes/toc.yml +++ b/release-notes/toc.yml @@ -1,32 +1,27 @@ toc: - file: index.md - - file: known-issues/index.md + - file: elastic-observability/release-notes.md children: - - file: known-issues/search-ui.md - - file: known-issues/elastic-observability.md - children: - - file: known-issues/elastic-apm.md - - file: known-issues/elastic-security.md - - file: known-issues/fleet-elastic-agent.md - - file: known-issues/elastic-cloud-serverless.md - - file: breaking-changes/index.md + - file: elastic-observability/known-issues.md + - file: elastic-observability/breaking-changes.md + - file: elastic-observability/deprecations.md + - file: elastic-apm/release-notes.md children: - - file: breaking-changes/elastic-observability.md - children: - - file: breaking-changes/elastic-apm.md - - file: breaking-changes/elastic-security.md - - file: breaking-changes/fleet-elastic-agent.md - - file: deprecations/index.md + - file: elastic-apm/known-issues.md + - file: elastic-apm/breaking-changes.md + - file: elastic-apm/deprecations.md + - file: elastic-security/release-notes.md children: - - file: deprecations/elastic-observability.md - children: - - file: deprecations/elastic-apm.md - - file: deprecations/elastic-security.md - - file: deprecations/fleet-elastic-agent.md - - file: deprecations/elastic-cloud-serverless.md - - file: elastic-observability.md + - file: elastic-security/known-issues.md + - file: elastic-security/breaking-changes.md + - file: elastic-security/deprecations.md + - file: elastic-cloud-serverless/changelog.md children: - - file: elastic-apm.md - - file: elastic-security.md - - file: fleet-elastic-agent.md - - file: elastic-cloud-serverless.md \ No newline at end of file + - file: elastic-cloud-serverless/known-issues.md + - file: elastic-cloud-serverless/deprecations.md + - file: fleet-elastic-agent/release-notes.md + children: + - file: fleet-elastic-agent/known-issues.md + - file: fleet-elastic-agent/breaking-changes.md + - file: fleet-elastic-agent/deprecations.md + - file: search-ui-known-issues.md \ No newline at end of file diff --git a/solutions/observability/apps/apm-agent-compatibility.md b/solutions/observability/apps/apm-agent-compatibility.md index 5ec8f4c297..78dda41b89 100644 --- a/solutions/observability/apps/apm-agent-compatibility.md +++ b/solutions/observability/apps/apm-agent-compatibility.md @@ -44,7 +44,7 @@ The chart below outlines the compatibility between different versions of Elastic | `1.x` | ≥ `6.5` | ::::{note} -Java agent < 1.43.0 not fully compatible with APM Server >= 8.11.0. Read more in [Known issues](/release-notes/known-issues/elastic-apm.md). +Java agent < 1.43.0 not fully compatible with APM Server >= 8.11.0. For more information, check [Elastic APM known issues](/release-notes/elastic-apm/known-issues.md). :::: diff --git a/solutions/observability/apps/switch-self-installation-to-apm-integration.md b/solutions/observability/apps/switch-self-installation-to-apm-integration.md index 54fae13069..e6bdcd6d50 100644 --- a/solutions/observability/apps/switch-self-installation-to-apm-integration.md +++ b/solutions/observability/apps/switch-self-installation-to-apm-integration.md @@ -20,7 +20,7 @@ mapped_pages: The {{stack}} ({{es}} and {{kib}}) must be upgraded to version 7.14 or higher. See the [{{stack}} Installation and Upgrade Guide](../../../deploy-manage/upgrade/deployment-or-cluster.md) for guidance. -Review the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html), and {{observability}} [What’s new](https://www.elastic.co/guide/en/observability/current/whats-new.html) content for important changes between your current APM version and this one. +Review the [Elastic APM release notes](/release-notes/elastic-apm/release-notes.md) and [Elastic {{observability}} release notes](/release-notes/elastic-observability/release-notes.md) for important changes between your current APM version and this one. ## Add a {{fleet}} Server [apm-integration-upgrade-2] diff --git a/solutions/observability/apps/upgrade-elastic-cloud-apm-server-standalone-to-8.md b/solutions/observability/apps/upgrade-elastic-cloud-apm-server-standalone-to-8.md index 39ee5fee66..a51656f911 100644 --- a/solutions/observability/apps/upgrade-elastic-cloud-apm-server-standalone-to-8.md +++ b/solutions/observability/apps/upgrade-elastic-cloud-apm-server-standalone-to-8.md @@ -16,7 +16,7 @@ This upgrade guide is for the standalone method of running APM Server. Only use Follow these steps to upgrade: -1. Review the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html), and {{observability}} [What’s new](https://www.elastic.co/guide/en/observability/current/whats-new.html) content. +1. Review the [Elastic APM release notes](/release-notes/elastic-apm/release-notes.md) and [Elastic {{observability}} release notes](/release-notes/elastic-observability/release-notes.md). 2. Upgrade {{ecloud}} to 9.0.0-beta1, See [Upgrade versions](../../../deploy-manage/upgrade/deployment-or-cluster.md) for instructions. 3. (Optional) Upgrade to the APM integration. Got time for one more upgrade? See [Switch to the Elastic APM integration](switch-to-elastic-apm-integration.md). diff --git a/solutions/observability/apps/upgrade-elastic-cloud-with-apm-integration-to-80.md b/solutions/observability/apps/upgrade-elastic-cloud-with-apm-integration-to-80.md index db67252ffa..05905a3b40 100644 --- a/solutions/observability/apps/upgrade-elastic-cloud-with-apm-integration-to-80.md +++ b/solutions/observability/apps/upgrade-elastic-cloud-with-apm-integration-to-80.md @@ -16,7 +16,7 @@ This upgrade guide is for the Elastic APM integration. Only use this guide if bo Follow these steps to upgrade: -1. Review the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html), and {{observability}} [What’s new](https://www.elastic.co/guide/en/observability/current/whats-new.html) content. +1. Review the [Elastic APM release notes](/release-notes/elastic-apm/release-notes.md) and [Elastic {{observability}} release notes](/release-notes/elastic-observability/release-notes.md). 2. Upgrade your {{ecloud}} instance to 9.0.0-beta1. See [Upgrade versions](../../../deploy-manage/upgrade/deployment-or-cluster.md) for details. The APM integration will automatically be upgraded to version 9.0.0-beta1 as a part of this process. ::::{note} diff --git a/solutions/observability/apps/upgrade-self-installation-of-apm-integration-to-8x.md b/solutions/observability/apps/upgrade-self-installation-of-apm-integration-to-8x.md index 578bc44eef..6908b3d019 100644 --- a/solutions/observability/apps/upgrade-self-installation-of-apm-integration-to-8x.md +++ b/solutions/observability/apps/upgrade-self-installation-of-apm-integration-to-8x.md @@ -18,7 +18,7 @@ This upgrade guide is for the Elastic APM integration. Only use this guide if bo ## Prerequisites [_prerequisites_9] 1. Prior to upgrading to version 9.0.0-beta1, {{es}}, and {{kib}} must be upgraded to version 7.17. To upgrade {{es}} and {{kib}}, see the [{{stack}} Installation and Upgrade Guide](https://www.elastic.co/guide/en/elastic-stack/7.17/upgrading-elastic-stack.html) -2. Review the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html), and {{observability}} [What’s new](https://www.elastic.co/guide/en/observability/current/whats-new.html) content. +2. Review the [Elastic APM release notes](/release-notes/elastic-apm/release-notes.md) and [Elastic {{observability}} release notes](/release-notes/elastic-observability/release-notes.md). ## Upgrade steps [_upgrade_steps_2] diff --git a/solutions/observability/apps/upgrade-self-installation-of-apm-server-standalone-to-8x.md b/solutions/observability/apps/upgrade-self-installation-of-apm-server-standalone-to-8x.md index f766a8fc24..94c77246f7 100644 --- a/solutions/observability/apps/upgrade-self-installation-of-apm-server-standalone-to-8x.md +++ b/solutions/observability/apps/upgrade-self-installation-of-apm-server-standalone-to-8x.md @@ -22,7 +22,7 @@ This upgrade guide is for the standalone method of running APM Server. Only use * To upgrade {{es}} and {{kib}}, see the [{{stack}} Installation and Upgrade Guide](https://www.elastic.co/guide/en/elastic-stack/7.17/upgrading-elastic-stack.html) * To upgrade APM Server to version 7.17, see [upgrade to version 7.17](https://www.elastic.co/guide/en/apm/guide/7.17/upgrading-to-717.html). -2. Review the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html), and {{observability}} [What’s new](https://www.elastic.co/guide/en/observability/current/whats-new.html) content. +2. Review the [Elastic APM release notes](/release-notes/elastic-apm/release-notes.md) and [Elastic {{observability}} release notes](/release-notes/elastic-observability/release-notes.md). ## Upgrade steps [_upgrade_steps] diff --git a/solutions/observability/apps/upgrade-to-version-8x.md b/solutions/observability/apps/upgrade-to-version-8x.md index ddd109d743..3ac478fb64 100644 --- a/solutions/observability/apps/upgrade-to-version-8x.md +++ b/solutions/observability/apps/upgrade-to-version-8x.md @@ -7,7 +7,7 @@ mapped_pages: This guide explains the upgrade process for version 9.0.0-beta1. For a detailed look at what’s new, see: -* [What’s new in {{observability}}](https://www.elastic.co/guide/en/observability/current/whats-new.html) +* [Elastic {{observability}} release notes](https://www.elastic.co/guide/en/observability/current/whats-new.html) * [What’s new in {{kib}}](https://www.elastic.co/guide/en/kibana/current/whats-new.html) * [{{es}} release highlights](https://www.elastic.co/guide/en/elasticsearch/reference/current/release-highlights.html) @@ -18,7 +18,7 @@ This guide explains the upgrade process for version 9.0.0-beta1. For a detailed * APM Server now only writes to well-defined data streams; writing to classic indices is no longer supported. * APM Server has a new {{es}} output implementation with defaults that should be sufficient for most use cases. -As a result of the above changes, a number of index management and index tuning configuration variables have been removed. See the APM [release notes](/release-notes/elastic-apm.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html) for full details. +As a result of the above changes, a number of index management and index tuning configuration variables have been removed. See the APM [release notes](/release-notes/elastic-apm/release-notes.md), [breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html) for full details. ## Find your upgrade guide [_find_your_upgrade_guide] diff --git a/solutions/observability/apps/upgrade.md b/solutions/observability/apps/upgrade.md index e4308c9bc8..f10dba0d15 100644 --- a/solutions/observability/apps/upgrade.md +++ b/solutions/observability/apps/upgrade.md @@ -8,11 +8,6 @@ mapped_pages: This guide gives general recommendations for upgrading Elastic APM. * [{{apm-agent}} compatibility](apm-agent-compatibility.md) -* [Breaking Changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html) +* [Breaking Changes](/release-notes/elastic-apm/breaking-changes.md) * [Upgrade to version 9.0.0-beta1](upgrade-to-version-8x.md) * [Switch to the Elastic APM integration](switch-to-elastic-apm-integration.md) - - - - -