AutoOps for Elasticsearch
Managing Elasticsearch just got a lot easier …
AutoOps for Elasticsearch significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, and real-time issue detection and resolution paths. And it's free for Elastic Cloud customers.
Every Elastic deployment is simple(r) to manage
Take a 2-minute tour now.
Frequently asked questions
Availability, access, licensing, and more
AutoOps for Elasticsearch significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, and real-time issue detection and resolution paths. By analyzing hundreds of Elasticsearch metrics, along with your configuration and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs.
AutoOps is rapidly expanding to Elasticsearch clusters on Elastic Cloud. It will become available in phases across cloud providers and regions — for both Elastic Cloud customers and trial users. Read more about the AutoOps roll out status.
AutoOps will be available for self-hosted and serverless customers with a different set of capabilities in the future.
AutoOps is currently available for Elasticsearch versions 7.17 and above.
Elastic Cloud Hosted users: If your cloud provider and region are listed on the AutoOps rollout page, you should see a button to access AutoOps on your deployment management page.
Hosted Trial users: When running a trial in a region where AutoOps is available, users should wait for up to 20 minutes for AutoOps to be applied, and up to a further 20 minutes for metrics and data to appear in AutoOps dashboards.
AutoOps's current feature set is available to Elastic Cloud Hosted customers at all subscription tiers. For more information, please refer to the subscriptions page.
Currently, AutoOps has a four-day retention period for all Elastic Cloud Hosted customers.
AutoOps metrics are stored internally within Elastic's infrastructure, not on customer deployments. Therefore, using AutoOps does not consume customer ECU.