Enhancements and bug fixes - January 2025
editEnhancements and bug fixes - January 2025
editThe following changes are included in this release.
Features
editUpdated EOL banner. Updates the informational banner about the deprecation of Enterprise Search.
[Fleet] Allow to configure xpack.fleet.enableManagedLogsAndMetricsDataviews. Adds the xpack.fleet.enableManagedLogsAndMetricsDataviews
setting to configure the automatic creation of global dataviews logs-*
and metrics-*
. (issue: #202807)
AutoOps expanded availability. AutoOps is now available to Elastic Cloud Hosted users in additional AWS regions: Oregon (us-west-2), Ireland (eu-west-1), and Singapore (ap-southeast-1). AutoOps will continue to be deployed to other AWS regions in the coming weeks. You can track AutoOps availability on the AutoOps regions page.
Template Optimizer. AutoOps now examines both new and updated templates, identifying specific fields that can be optimized for better performance.
New Deployment Performance Metrics Charts. AutoOps provides aggregate metrics at the cluster level for key performance indicators. The data is tier-based, offering users a comprehensive understanding of each tier and the entire cluster.
Enhancements
editPassthrough hosted otel bound firehose requests. Passthrough hotel bound firehose requests and avoid processing by the proxy’s firehose middleware.
Deprecate Cloud Defend billing alerts. Following the deprecation of Cloud Defend in Serverless, removes the billing logic associated with the feature.
AutoOps shards view improvements. Improved navigation include a new time slider, ability to filter nodes by tier, and revised color schema.
AutoOps feedback button. A new feedback button has been introduced, allowing users to easily share their thoughts and suggest ideas for improvement.
Bug fixes
editAdd the field dry_run to the rest of stateless components. Adds the field dry_run
to stateless components in the response of the endpoint GET api/v1/deployments/{DEPLOYMENT_ID}
. Also removes a check in the UI that is no longer required.
Bulk item level failures are treated as successfully delivered. Check the response body for bulk item level failures even when the HTTP request returns 200 from Elasticsearch. (issue: #11768)