Enhancements and bug fixesedit

The following changes are included in this release.

Featuresedit

Official Elastic diagnostics tool now supported. In an effort to streamline how we support you, Elasticsearch Service now integrates the Elasticsearch and Kibana diagnostics tooling that comes with the stack.

Enhancementsedit

Limit compatible versions for CCS/CCR, starting with 8.0. This release of Elasticsearch Service updates the rules for which versions are compatible to be used together for cross-cluster search and cross-cluster replication.

Add Kibana diagnostics. Adds the POST /deployments/{deployment_id}/kibana/{ref_id}/diagnostics/_capture endpoint to retrieve Kibana diagnostics.

Track machine learning usage in all environments. Track the machine learning feature via the GET /api/v1/saas/billing/usage/features API in all environments.

Reduce docker health-related plan failures. When docker is not healthy, allocators are not able to start new instances, which will cause failed plans. This change makes sure that allocators where docker is not healthy are avoided when allocating new instances.

Update Backend Response Time to include a list of attempted instances. Adds a list of backend_response_time for all the instances that the proxy attempted. This helps to see how many instances the proxy tries to connect to and the response time from each of those instances.

Don’t run SetQuorumSize for 7.x clusters. Plans for version 7.x and later clusters will no longer execute the step "Setting Elasticsearch cluster quorum size".

Improve the deployment pricing table. Now you can filter the deployments pricing table page by the marketplace provider.

When upgrading to 7.14, default to migrating to node_roles. A deployment being upgraded to version 7.14 or higher defaults to migrating from the deprecated node_type to node_roles.

Add Elasticsearch diagnostics. Adds the POST /deployments/{deployment_id}/elasticsearch/{ref_id}/diagnostics/_capture endpoint to retrieve cluster diagnostics.

Bug fixesedit

Make sure every cluster data contains a self-reference to the same cluster. Fixes the cluster metadata so internal requests to Kibana (for example, the Kibana proxy endpoints) work when using traffic filters.

Remove the APM rate_limit max values. Removes the maximum value limits of 100, 100 and 3000 for the APM server settings:

  • apm-server.rum.rate_limit
  • apm-server.frontend.rate_limit
  • apm-server.rum.event_rate.limit

Prevent crashes on pages translated with Google Translate. Fixes crashes in certain interactions of the login, reset password, and billing pages when they are translated using Google Translate.

Fixed a bug that applied the default traffic filters when a deployment is edited. When existing deployments were edited, even for no-op plans, the default traffic filters were being applied.

Respect extendedMaintenance during rolling step. Fixed a bug which caused plans to disable maintenance mode too early when applying rolling changes to nodes during a plan which uses extended maintenance.

Deprecationsedit

Secure tunneling page is deprecated. Our Tunneling SSL documentation page has been marked as deprecated and will be removed in an upcoming release. We do not recommend using HTTP clients to connect to Elastic Cloud. If you need to do so, you should use a reverse proxy setup. If you have any concerns, please contact support.

Whitelist the vis_type_vega.enableExternalUrls . In Elastic Stack version 8.0.0, the vega.enableExternalUrls YAML setting will be removed (elastic/kibana#112643). Use the vis_type_vega.enableExternalUrls setting instead.

Supports timelion.ui.enabled until v7.16. Removes the whitelisted timelion.ui.enabled kibana.yml setting due to the removal of the Timelion app in the Elastic Stack version 7.16.

Adds a max version in the vis_type_table.legacyVisEnabled setting. The vis_type_table.legacyVisEnabled setting is supported until Elastic Stack version 7.16.x.

Docsedit

Add a new section on Best practices for managing your data. We have added new guidelines to help our customers manage their data when they use Elasticsearch Service. These best practices are also accessible from the Shared responsibilities page.

Add Node.js application logging tutorial to Elasticsearch Service docs. As a further expansion to our Elasticsearch Service ingestion documentation, we’ve added a new guide Ingest logs from a Node.js web application using Filebeat.