Loading

AutoOps FAQ

Serverless ECH ECK ECE Self-Managed

Whether you are using AutoOps in your Elastic Cloud Hosted deployment, Serverless project, or self-managed cluster, find answers to some common questions about it on this page.

General AutoOps questions

Questions about AutoOps for self-managed clusters

Setting up AutoOps for self-managed clusters

Collected metrics and data in AutoOps for self-managed clusters

What does AutoOps do?
AutoOps for Elasticsearch simplifies cluster management by providing performance recommendations, resource utilization and cost insights, real-time issue detection, and resolution paths. By analyzing hundreds of Elasticsearch metrics, your configuration, and usage patterns, AutoOps provides operational and monitoring recommendations that reduce administration time and hardware costs.
Where is AutoOps available?
In the regions where it has been rolled out, AutoOps is automatically available in Elastic Cloud Hosted deployments and can be set up for ECE, ECK, and self-managed clusters through Cloud Connect.

Why can't I see AutoOps in some deployments and projects? AutoOps is rolling out in phases across CSPs and regions, so you may not see it if your deployment or project is in a region where AutoOps is not available yet. AutoOps is currently not available in Azure and GCP.

How is AutoOps licensed?

For Elastic Cloud Hosted deployments and Serverless projects, AutoOps is available to Elastic Cloud customers at all subscription levels at no additional cost, and it does not consume ECU.

Using AutoOps for self-managed clusters (ECE, ECK, or standalone) on-premise or in private cloud environments through Cloud Connect is included with self-managed Enterprise licenses and self-managed free trials. This does not consume ECU.

Does AutoOps monitor the entire Elastic Stack?
AutoOps is currently limited to Elasticsearch (not Kibana, Logstash, or Beats).
Can AutoOps automatically resolve issues?
AutoOps only analyzes metrics and is a read-only solution.
Which versions of Elasticsearch are supported in AutoOps for Elastic Cloud Hosted and self-managed clusters?
AutoOps is compatible with supported Elasticsearch versions (7.17.x and above).
How long does Elastic retain AutoOps data?
AutoOps has a 10 day retention period.
Where are AutoOps metrics stored, and does AutoOps affect customer ECU usage?
AutoOps metrics are stored internally within the Elastic infrastructure, not on customer deployments. Using AutoOps does not consume customer ECU.
Has AutoOps replaced Stack Monitoring?
Currently, AutoOps has many of the same features as Stack Monitoring as well as several new ones. However, it only provides insights on Elasticsearch and analyzes metrics, not logs. Read more in AutoOps and Stack Monitoring comparison.
Does AutoOps for self-managed clusters incur additional costs?

Using AutoOps for self-managed clusters (ECE, ECK, or standalone) on-premise or in private cloud environments through Cloud Connect is included with self-managed Enterprise licenses and self-managed free trials. This does not consume ECU.

Does shipping metrics data to Elastic Cloud incur additional costs?

Elastic does not charge extra for this service, but your cloud service provider (CSP) might. When sending metrics data from your cluster in a CSP region to Elastic Cloud, shipping costs are determined by your agreement with that CSP.

You can choose the CSP region where your data is stored.

Which deployment types can be connected to AutoOps through Cloud Connect?
You can connect to AutoOps on a standalone Elastic Stack, ECE (Elastic Cloud Enterprise), or ECK (Elastic Cloud on Kubernetes) deployment, both on-premise and in private cloud environments.
Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?

This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.

For Elastic Cloud Hosted clusters, AutoOps is set up and enabled automatically in all supported regions, and can be accessed from the deployment overview page.

Can I use AutoOps for my clusters if my environment is air-gapped?
Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to Elastic Cloud. For air-gapped environments, we plan to offer a locally deployable version in the future.
Can I use macOS to install Elastic Agent for this feature?
macOS is not a supported platform for installing Elastic Agent and connecting your clusters to AutoOps.
Do I have to define an Elastic IP address to enable the agent to send data to Elastic Cloud?

You may need to define an IP address if your organization’s settings will block the agent from sending out data.

To enable IP ranges, Elastic Cloud offers a selection of static IP addresses. All traffic directed to Elastic Cloud deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination.

For more information, refer to Elastic Cloud Static IPs.
Where are metrics stored in AutoOps for self-managed clusters?

You can choose where to store your metrics from the following AWS regions:

Region Name
us-east-2 US East (Ohio)
eu-west-1 EU (Ireland)
ap-northeast-1 Asia Pacific (Tokyo)

More regions are coming soon.

What information does Elastic Agent gather from my cluster?

Elastic Agent only extracts and sends cluster metrics to Elastic Cloud, not the underlying data within your cluster. The following metrics are collected:

API Description Collected data
_cat/shards Returns detailed information about the shards within the cluster Shard states, node allocation, index names, sizes, and replica information
_nodes/stats Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics CPU usage, memory utilization, thread pools, file system stats
_cluster/settings Returns the settings configured for the cluster Persistent and transient settings such as cluster-wide configurations
_cluster/health Provides information about the overall health of the cluster Status (green/yellow/red), number of nodes, number of shards
_cat/template Lists all index templates in the cluster Template names, patterns, and basic settings
_index_template Retrieves composable index templates Index settings, mappings, and aliases
_component_template Fetches component templates used for building index templates Metadata for re-usable mappings and settings
_tasks Displays information about currently running tasks on the cluster Task descriptions, start times, running nodes, and execution details
_template Retrieves legacy index templates Similar to composable index templates but in older format
_resolve/index/* Resolves index, data stream, and alias names to their current definitions Mappings between names and underlying data objects
How does AutoOps gather data from my cluster and ensure its security?

AutoOps gathers data from your cluster using two protocols:

  • HTTP request: Made to our Cloud Connected API to register your cluster with Elastic Cloud and gather registration-related data.
  • OpenTelemetry Protocol (OTLP): Used to gather all other operational data.

Each channel is authenticated using an API key or token to ensure your data's security. The following table offers more details:

Protocol Data extracted Port Authentication method
HTTP Basic cluster information from the / endpoint

License information from the /_license endpoint		 443: standard HTTPS port Uses an Elastic Cloud API key which is limited for use with Cloud Connect only.
OTLP over HTTP Operational information 443: standard HTTPS port Uses an AutoOps token which is functionally equivalent to an API key.
Can I view the data gathered by Elastic Agent?
You can use the autoops_es_debug.yaml config file to export and review a sample of the data gathered from your cluster and sent to Elastic Cloud.