Elastic Cloud Hosted breaking changes
Elastic Cloud Hosted breaking changes can impact your Elastic applications, potentially disrupting normal operations. Carefully review them and take the necessary steps to mitigate any issues.
In addition, before upgrading your hosted deployments, review the breaking changes for any Elastic Stack applications that you're using.
To view breaking changes from December 2024 and earlier, go to Elastic Cloud release notes.
Api
Remove amount-based thresholds from budget alerts.
Removes amount-based thresholds from budget alerts. Thresholds now support percentages only, and the threshold_type field is optional and defaults to percentage.
Impact
Requests to create or update a budget alert with threshold_type set to amount are rejected with an HTTP 400 error, as are thresholds greater than 100. Existing amount-based thresholds were migrated to percentage thresholds.
Action
Update API clients to send each threshold as a percentage of the budget, from 0 to 100. If a client sends amount-based thresholds, convert each value to a percentage first, then set threshold_type to percentage or omit it. Omitting threshold_type does not convert the value. For example, an amount of 50 on a budget of 1,000 must be sent as 5.
Removed deprecated _upgrade endpoint
The deployments/<deployment_id>/<resource-kind>/<ref_id>/_upgrade endpoint was already deprecated and has now been removed. To upgrade a deployment using the API, you should instead use the /deployments/{deployment_id} endpoint.
Removed Elasticsearch and Kibana URLs from supported settings
ApmSystemSettings, IntegrationsServerSystemSettings, KibanaSystemSettings and EnterpriseSearchSystemSettings no longer support elasticsearchUrl and kibanaUrl fields.