Loading

AutoOps for self-managed clusters FAQ

ECK ECE Self-Managed

Find answers to your questions about AutoOps for ECE, ECK, and self-managed clusters.

General questions

Questions about setting up

Questions about collected metrics and data

Why should I use AutoOps for my clusters?
AutoOps simplifies the operation of your Elasticsearch clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues.
Does this feature require additional payment?

Using AutoOps for ECE, ECK, and self-managed clusters through Cloud Connect is included with your self-managed Enterprise license and self-managed free trials.

Is there an added cost for shipping metrics data to Elastic Cloud?

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 will be determined by your agreement with that CSP.

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

Which versions of Elasticsearch does AutoOps support?
AutoOps is compatible with supported Elasticsearch versions (7.17.x and above).
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.
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 AutoOps metrics stored?

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

Region Name
us-east-2 Ohio
eu-west-1 Ireland
ap-northeast-1 Tokyo

More regions are coming soon.

What information does Elastic Agent extract 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 through 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 Operational information 4318: standard OTLP HTTP port

This service will be exposed on port 443 in the future.		 Uses an AutoOps token which is functionally equivalent to an API key.