Better feature usage tracking, new cost and usage analysis page, and moreedit

Release highlightsedit

Feature usage tracking for self-service customers. It is now possible for customers to analyze their Elastic Cloud feature usage and choose the subscription level that best fits their needs.

Cost and usage analysis page. To help users better understand their costs, we have introduced a new Usage analysis page under Account & Billing. The Usage analysis page allows you to filter historical data and break down usage by deployment, as well as by product. For annual and overages customers, it also shows how many credits will be applied for the current bill cycle.

For the full list of release changes, see below.

Featuresedit

Unhide deployment aliases fields from Deployments API. Deployment Alias field alias added to support user-friendly URLs for deployment resources.

Log delivery health status. Callout section lists all observability health issues for a deployment.

Add data tiers to UI. Data tiers and their associated Elasticsearch node.roles are now supported in the UI.

Enhancementsedit

Updated the user menu hover and focus state. Fixes minor visual bugs in the user menu. The buttons were not the full width of their parent, and the focus state was emphazising that issue. In addition, the moon icon had the wrong colour.

Allow the vis_type_table.legacyVisEnabled kibana setting. Adds new datatable setting vis_type_table.legacyVisEnabled to allow list. This setting can be used to switch to the legacy datatable.

GovCloud Registration page. Allows GovCloud users to self-service registration.

Start using Metricbeat for monitoring for 7.6+ clusters. For 7.6+ deployments, monitoring will now be implemented using Metricbeat since legacy collection monitoring is deprecated and planned for removal. Any deployment update executed on a monitored 7.6+ deployment will undergo a one-time rolling plan change to transition the deployment to Metricbeat-based monitoring.

Allow Kibana CORS settings on Cloud. Cloud adds Cross-Origin Resource Sharing (CORS) support for Kibana with the following settings: server.cors.enabled - Set to true to allow cross-origin API calls. Default: false. server.cors.allowCredentials - Set to true to allow browser code to access the response body whenever the request is performed with user credentials. Default: false. server.cors.allowOrigin - List of origins permitted to access resources. You must specify server.cors.allowOrigin when server.cors.allowCredentials: true. Default: ["*"]

Implement new deployment features navigation and page. Adds new deployment features ESS navigation item and page.

Remove subscription from the user menu. The subscription level badge is removed from the user menu. Users should navigate to Account & Billing to view their subscription level.

Bug fixesedit

Updating disk notifications toggle to reflect default setting. Fixes default UI setting for disk notifications.

chmod user bundles after unpacking them. User bundles with read-only files or folders will no longer cause nodes to boot loop on restart.

Fix stuck allocator task scheduler. Fixes the issue with duplicated ticks and leader latches in ClusterTaskScheduler by introducing a scheduler with a single fixed tick loop.

No Kibana upgrade. Fixes a bug where a disabled or terminated Kibana would not allow users to upgrade their deployment version.

Fix company info validation. Fixes a bug that was improperly validating user inputs when they were updating their credit card information.

Fix action after enabling monitoring on a deployment. Fixes issue when enabling Logs and metrics on a deployment. User sees the Enable button before the status flips to pending and shows the new monitoring deployment.

Fix YAML parser in UI. Fixes a bug where attempting to save YAML settings that only include comments resulted in an error message: The YAML settings are invalid, please check your syntax.

Re-enable allocations when major version upgrade fails. Re-enables allocations by setting them back to all after a (rolling) major version upgrade fails. Allocations are also set to primaries and not none before rolling an instance, as recommended by Elasticsearch.

Fix partial upgrade bug. Fixes a bug preventing the upgrade of deployments with Elasticsearch instances on different versions.

Remove issue time so that JWT don’t change from plan to plan. Fixes an issue where when log delivery is enabled, a force restart plan causes instances to be created.

Fix Kibana metrics link errors. Fixes errors that are shown in Kibana when following metrics links from logs and metrics UI.