Installation FAQs

Quick links

What is AutoOps?

AutoOps is a complete solution for operating and optimizing Elasticsearch & OpenSearch. AutoOps prevents & resolves issues, cuts down administration time, and reduces hardware costs. Available along with Opster’s proactive support, you no longer have to worry about your search operation – Opster takes charge of it.

Does AutoOps work with Elasticsearch or OpenSearch?

Both! AutoOps, and all of Opster’s solutions, support customers using both Elasticsearch and OpenSearch.

What versions of Elasticsearch/OpenSearch are supported by AutoOps?

AutoOps provides full support for the most up-to-date releases of Elasticsearch, including version 1.7.6 and all subsequent versions, as well as OpenSearch version 1.0.0 and any subsequent versions.

Can I use AutoOps if my cluster is run by managed services like Elastic Cloud or Amazon OpenSearch service?

Yes. You can benefit from AutoOps whether your cluster is self-hosted or run by a managed service like Elastic Cloud, AWS-managed OpenSearch, etc.

You can install Opster Metricbeat on your preferred environment, such as any Linux distribution, Ubuntu Docker, Docker Compose, Windows machines and so on.

Is Opster SOC2 compliant?

Yes. Opster is SOC2 type II certified.

Why do I need to install Opster Metricbeat?

In order to analyze your cluster data, Opster uses a lightweight Go agent, which is a fork of Metricbeat, to connect to the Elasticsearch/OpenSearch API endpoint. Opster’s version allows AutoOps to collect different metrics from the cluster. 

Opster is SOC-2 certified and the Metricbeat only sends machine metrics and stats, trusted by Fortune 500 companies and other leading organizations.

What information does AutoOps extract?

AutoOps only fetches cluster stats and metrics. 

Some of the stats collected include:

/_cat/shards –

/_nodes/stats –

/_cluster/settings –

/_cluster/health –

/_nodes/hot_threads –

/_cat/template –

/_tasks –

/_ilm/explain –

/ – this just accesses the cluster name & ID and is treated as Ping API

How long does Opster retain my data?

Most of the stats collected are kept for 7 days. Other aggregative information is stored for a longer period of time to enable users to compare KPIs over different time periods.

Can I use the same Opster token to connect more than one cluster?

Yes. A unique Opster token is provided per account. You can reuse the same token to connect to more than one cluster. Please note that each cluster needs its own Metricbeat installation.

How do I delete my account / delete my data after my trial is complete?

Simply contact Opster support to request account and/or data deletion. The request should be submitted in writing through the support portal on the bottom right of your screen, or via email to

Do I need to set up special permissions to connect my cluster to AutoOps?

If your cluster is run by a managed service, you may have to add additional permissions to allow the extraction of the needed stats.

  • Cluster privileges: monitor, monitor_ilm, monitor_snapshot
  • Index privileges:
  • Indices: *
  • Privileges: monitor


  • Cluster level permission: CLUSTER_MONITOR, INDICES_ALL.
  • Index level permission: Indices: *

If you’re required to open an IP/port on your firewall to ship the data, please add the following:

  • Address:
    • –
    • –
  • Port: 80, 433 or 5044 (less recommended)

What type of support does Opster provide during the free trial?

During the trial period, Opster provides complete support to assist with any questions about the installation process. Opster’s expert team is always available to provide support with implementing the recommendations provided by AutoOps.

Beyond this, Opster’s experts review the cluster analysis results, share insights and are available for a free review session.

After installing Opster Metricbeat, when can I start seeing events in AutoOps?

AutoOps usually starts showing stats and generating events around 15 minutes after the initial receipt of data from your cluster.