Organization and billing API updates, and moreedit

The following changes are included in this release.

Featuresedit

Revert the 8.0.0 specific format parsing. Elasticsearch Service now expects the same format for 8.0 snapshot API responses as was used in version 7.x.

Add live "in-app" EOL notifications. Add notifications for deployments which are approaching, or have reached EOL status.

Enhancementsedit

Adapt user settings for 7.17 and 8.0. Follow up for allowed user overridable config changes for APM Server 7.17 and 8.0.

Accessibility fix: added aria-label to "remove contact" button. Add screen reader label to the button for removing contacts.

Breaking down billing dimensions costs in the responses. Change the responses for the Costs Analysis APIs. In particular, the CostsOverview renames resources to capacity and it replaces the data_transfer_and_storage field with its equivalent breakdown into capacity, data_in data_out, data_internode, storage_bytes and snapshot_storage fields.

Elasticsearch deprecation logger level (ES7.16). Incorporate version 7.16 and newer deprecation level (CRITICAL/WARN) changes.

This commits updates deprecation log config to the ES7.17. Updates elasticsearch log4j config for 7.17 to contain additional field x-elastic-product-origin (and a few others that needed to be included).

Add APM auto-create settings to cloud allow list. Allow xpack.apm.autocreateIndexPattern (for Kibana versions 7.6.0-7.16.0) and xpack.apm.autoCreateDataView (renamed for ≥ 8.0.0) to be configured for the APM UI in Kibana on Cloud deployments.

Update disable sandbox option for reporting. Kibana configuration option xpack.reporting.capture.browser.chromium.disableSandbox has been renamed to xpack.screenshotting.browser.chromium.disableSandbox in 8.0.

Make organization APIs public. Organization management APIs are now available in the Elasticsearch Service public API.

Bug fixesedit

Bump co.elastic.support:diagnostics version to 8.2.7. Use version 8.2.7 of the Elastic support diagnostics, which includes the fix for Kibana version 8.0.

Show APM if terminated APM exists after upgrade to 8.0. Fixes a bug where if APM was terminated before or after upgrading from 7.17 to 8.0, the side navigation would show a menu item for Integrations Server instead of APM/Fleet.

Use vault on the bucket_capacity_show command. Change the password source for the bucket_capacity_show command to be the vault.

Hide APM settings when in managed mode. Hides APM user settings when APM is in managed mode as user settings are not supported.

Show operations when pending plan is running if it isn’t a create plan. Fixes a bug where the Operations page is not displayed when a plan is in progress.

Disable logging and metrics warnings on downscaled topologies. Improves the observability configuration checks that produce alerts, reducing the number of false positives that aren’t applicable to downscaled configurations.

Deprecationsedit

Remove obsolete proxy settings from internal models. The proxy settings APIs have been deprecated because these settings were no longer used. The API endpoints still exist, but will not update or return actual settings anymore. In addition, the Adminconsole no longer takes the expected_proxies_count setting into account when it determines the overall proxies health.

Comment out updating enable disk allocation setting. You can no longer disable disk-based shard allocation through the plan. If you need to do so, you can do it directly through the Elasticsearch cluster settings API.

Docsedit

New guide to migrate Elasticsearch data. Adds a new step-by-step guide on how to migrate from a self-managed, self-signed cluster to Elasticsearch Service by using a remote reindex.

Update node content. Updated the description on how nodes are automatically calculated based on the size chosen. Also updated the screen capture.

Update 6.8 upgrade documentation to indicate EOL. We’ve updated the Elastic Stack version 6.x upgrade instructions to indicate that version has reached the EOL date. If you are running this version, we recommend you to upgrade your deployment to a more current version of the Elastic stack.