elastic · KOTungseth · Mar 17, 2025 · Mar 13, 2025 · Mar 13, 2025 · Mar 13, 2025
@@ -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

@@ -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/'"

@@ -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)
 

@@ -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.

@@ -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.

@@ -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.
 

@@ -0,0 +1,6 @@
+toc:
+  - file: release-notes.md
+    children:
+      - file: known-issues.md
+      - file: breaking-changes.md
+      - file: deprecations.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.
 

@@ -0,0 +1,5 @@
+toc:
+  - file: changelog.md
+    children:
+      - file: known-issues.md
+      - file: deprecations.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**<br> Impact of the breaking change.
+% **Action**<br> 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.
+::::
@@ -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.

@@ -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.
 

@@ -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]
+### 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])
@@ -0,0 +1,6 @@
+toc:
+  - file: release-notes.md
+    children:
+      - file: known-issues.md
+      - file: breaking-changes.md
+      - file: deprecations.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]).
 ::::