Elastic Consumption Units, and more

Introducing Elastic Consumption Units!

Prepaid billing just got easier. For new annual customers on the prepaid consumption billing model, all Elasticsearch Service usage is now conveniently metered and billed in Elastic Consumption Units (ECUs). All other customers will be migrated to this model at a future date. To learn more, check Using Elastic Consumption Units for billing and our Billing FAQ.

Add transactionGroupBucketSize to allow list. Added support for the xpack.apm.ui.transactionGroupBucketSize APM configuration setting in the Kibana User Settings editor for versions 7.16.0 and later.

Add APM configuration settings to cloud allow list. The following APM configuration settings are now supported and can be edited in the Kibana User Settings editor:

Set nameid_format in SAML config for SSO. Elasticsearch Service now sets nameid_format explicitly when configuring SAML realms for SSO.

Make the document-level security and field-level security features available in all environments. The DLS and FLS features are now accessible through the GET /api/v1/saas/billing/{organization_id}/features API in all environments.

Make the searchable snapshots feature available in all environments. The searchable-snapshots feature is now accessible through the GET /api/v1/saas/billing/usage/features API in the all environments.

Add workplace_search.content_source.salesforce.enable_cases setting. Added configurable settings for Salesforce content source in Workplace Search (workplace_search.content_source.salesforce.enable_cases) that allow you to enable or disable synchronization of Case Salesforce objects.

Enable expansion of time range for Billing Usage page . We removed the three month limit that applied when querying deployment information on the billing Usage page.

Add help text to region field. When creating a traffic filter a region field must be set, however there can be a few different concepts of region at this time. This PR adds some clarifying help text to the region field shown on the Create traffic filter UI.

EOL warnings in stack versions. Displays an End of Life warning on the Elasticsearch Service UI where the stack version and deployment lists are displayed, and the individual deployment pages, for Elastic Stack packs and deployments using versions 5.x and 2.x.

Do not meter hidden deployments. This PR updates the CTS feature-usage task to check if the cluster instance it is about to meter usage for belongs to a hidden deployment. If so, the task does not perform any metering of that instance.

Show failed status and error in heap dump UI. Fixed a UI error when heap dump capture fails.

Depreciation of CCS deployments. The dedicated Cross cluster Search deployment type is deprecated in preparation for its removal in Elasticsearch Service 3.0. It is no longer listed when creating new deployments through the UI.

Remove Azure Marketplace docs in favour of Azure integrated offering. Elasticsearch is now offered as a native service in the Azure console, providing consolidated billing with your Azure bill, simplified data ingestion for Azure logs and metrics, support for Private Link, and more. As a result of this new native service offering, Elasticsearch Service is no longer offered as part of the Azure Marketplace. To learn more the new integration, check our Native Azure integration documentation.

Revove kibana.defaultAppId. The Kibana user setting kibana.defaultAppId has been removed from the Elasticsearch Service allow list for version 8.0, as the property will no longer be supported beginning in version 8.

Overhaul deployment health landing page. We’ve updated our Keeping your deployment healthy page to help you find the resources needed to ensure the ongoing health of your Elasticsearch Service deployments, and to troubleshoot any problems when they arise.

Traffic Filter API Example. We’ve added several examples to help you manage traffic filters in Elasticsearch Service using the API.

Improve memory pressure documentation We’ve updated the monitoring scenario documentation for memory pressure to include additional guidance on sizing, workload, sharding, data retention, and performance tuning. Learn more …​