elastic · wajihaparvez · Oct 10, 2025 · Oct 17, 2025 · Oct 19, 2025 · Oct 21, 2025
@@ -3,6 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitor-elasticsearch-cluster.html
   - https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html
 applies_to:
+  serverless:
   deployment:
     ess: all
     ece: all
@@ -36,6 +37,7 @@ The following sections provide more details.
 ### AutoOps (recommended)
 
 ```{applies_to}
+serverless:
 deployment:
   ess:
   self:
@@ -45,7 +47,7 @@ deployment:
 
 AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.
 
-In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
 
 ### Stack monitoring
 

@@ -2,8 +2,8 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-autoops.html
 applies_to:
-  deployment:
   serverless:
+  deployment:
     ess: all
     self:
     ece:
@@ -48,7 +48,7 @@ AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing r
 
 ## AutoOps availability
 
-In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
 
 AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
 
@@ -65,7 +65,8 @@ AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment
 
 In this section, you'll find the following information:
 
-* How to [access AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
+* How to [use AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
+* How to [use AutoOps in your {{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md).
 * How to [connect your ECE, ECK, or self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) to AutoOps.
 * [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
 * What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).

@@ -0,0 +1,18 @@
+---
+applies_to:
+  serverless:
+navigation_title: Access AutoOps in your project
+---
+
+# How to access AutoOps in your serverless project
+
+To access AutoOps in your serverless project, follow these steps:
+
+1. Log in to your {{ecloud}} account.
+2. Locate the serverless project you want to work on and select **Manage**.
+3. On the project overview page, in the **Usage and Performance** section, select **View in AutoOps**.
+
+:::{note} 
+AutoOps for {{serverless-full}} is only available in supported [regions](ec-autoops-regions.md#autoops-for-serverless-full-regions), with the exception of the **Search AI Lake** view, which is available in all CSP regions across AWS, Azure, and GCP.
+:::
+
@@ -0,0 +1,87 @@
+---
+applies_to:
+  serverless:
+navigation_title: For {{serverless-full}}
+---
+
+# AutoOps for {{serverless-full}}
+
+For [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md) projects, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-serverless-full-regions). More regions are coming soon. 
+
+## How AutoOps monitors your serverless project
+
+In your {{serverless-full}} project, Elastic ensures that the appropriate resources are adequately provisioned and autoscaled so that your workloads run efficiently. This is why {{serverless-full}} is billed based on the effective usage of compute and storage resources.
+
+:::{tip} 
+For more information about how {{serverless-full}} is priced and packaged, refer to the following pages:
+* [{{serverless-full}} pricing page](https://www.elastic.co/pricing/serverless-search)
+* [{{serverless-full}} pricing and packaging blog post](https://www.elastic.co/blog/elastic-cloud-serverless-pricing-packaging)
+:::
+
+Since your monthly serverless bill is directly related to how many resources have been consumed, it's important for you to understand why your consumption fluctuates and how past usage was influenced by your project's performance. This information lets you adapt your workloads accordingly and have better control over your future bills.
+
+This is where AutoOps comes in. With AutoOps for Serverless, you can:
+
+* understand and monitor your usage patterns through project-level and index-level performance metrics.
+* access several curated dashboards to look at your project from all the different angles.
+* have full visibility into the main serverless billing dimensions.
+
+:::{note}
+To align with the [new {{serverless-full}} architecture](https://www.elastic.co/blog/journey-to-build-elastic-cloud-serverless#rethinking-architecture:-from-stateful-to-stateless), AutoOps for Serverless does not include monitoring API endpoints such as [node statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) and [cluster statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-stats). These endpoints are included in [](ec-autoops-how-to-access.md) and [](cc-autoops-as-cloud-connected.md).
+:::
+
+## AutoOps for Serverless billing dimensions
+
+AutoOps for serverless focuses on different [billing dimensions](/deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md) related to compute and storage, which are explained in the following subsections.
+
+### Compute billing dimensions
+On [{{es-serverless}} projects](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md), the main compute-related billing dimension is called a **Virtual Compute Unit (VCU)**. 1 VCU contains 1GB of RAM and the corresponding vCPU and local storage for caching. 
+
+There are three main types of VCUs:
+* **Search VCUs** powering the search tier, which handles all search operations.
+* **Indexing VCUs** powering the indexing tier, which handles all data indexing operations.
+* **Machine learning VCUs** powering the machine learning tier, which handles all ML-related operations such as inference, anomaly detection, data frame analytics, transforms, and more.
+
+VCUs materialize the load that each of the above tiers has to sustain to respond to your search, indexing, and machine learning needs respectively. As the load of a given tier fluctuates above or below some pre-defined thresholds, the tier will autoscale accordingly to accommodate that load.
+
+:::{tip} 
+For more information about how autoscaling works in serverless, refer to the following blog posts:
+* [Search tier autoscaling](https://www.elastic.co/search-labs/blog/elasticsearch-serverless-tier-autoscaling)
+* [Ingest autoscaling](https://www.elastic.co/search-labs/blog/elasticsearch-ingest-autoscaling)
+:::
+
+:::{admonition} Example: How search VCU billing is calculated
+Let's say your constant search workload requires 4GB of RAM, which means your search VCU usage for one day will be 4 search VCUs/hour * 24 hours = 96 VCUs. 
+
+Given that 1 search VCU = [$0.09/hour](https://www.elastic.co/pricing/serverless-search), this translates to $8.64 for that day.
+:::
+
+### Storage billing dimensions
+
+On [Observability](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md) and [Security](/deploy-manage/cloud-organization/billing/security-billing-dimensions.md) Serverless projects, one storage-related billing dimension is called the **Ingest rate**, which represents the volume of data (in GB) ingested per unit of time.
+
+On all [{{es}}](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md), [Observability](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md), and [Security](/deploy-manage/cloud-organization/billing/security-billing-dimensions.md) Serverless projects, the main storage-related billing dimension is called **Storage retained** or **Retention**, and it represents the total volume of data (in GB prorated over a month) retained in your project.
+
+:::{admonition} Example: How ingest rate and storage retained billing is calculated
+Let’s say you ingest 1TB of data into your Observability project.
+
+* **Ingest rate**: Given that 1GB ingested per hour = [$0.105](https://www.elastic.co/pricing/serverless-observability), your ingest rate cost will be $107.2.
+* **Retention**: Given that 1GB retained per hour = [$0.018](https://www.elastic.co/pricing/serverless-observability) and assuming it took one hour to ingest 1TB of data, that 1TB will be billed 1.42GB for that slice of one hour (1TB/720 hours per month), which translates to $0.025. Each subsequent hour in that month will cost the same.
+:::
+
+## Coming soon
+
+The following features are coming soon to AutoOps for Serverless:
+
+* An **Indexing tier** view, which will show you how indexing performance influences your use of ingest VCUs.
+* A **Machine learning tier** view, which will provide insight into your machine learning jobs and inference performance, as well as token usage.
+* Visibility into other billing dimensions such as data transfer out of {{ecloud}} and the various Observability and Security add-ons.
+
+## Section overview 
+
+In this section, you'll find the following information:
+
+* How to [access AutoOps in your serverless project](access-autoops-for-serverless.md).
+* How to use the [Search tier view](search-tier-view-autoops-serverless.md) to see the impact of search performance on your use of search VCUs.
+* How to use the [Search AI Lake view](search-ai-lake-view-autoops-serverless.md) to drill down into your storage-related usage.
+
@@ -12,7 +12,7 @@ products:
 
 # AutoOps for self-managed clusters
 
-Use [AutoOps](/deploy-manage/monitor/autoops.md) with your ECE ({{ece}}), ECK ({{eck}}), or self-managed clusters through [Cloud Connect](/deploy-manage/cloud-connect.md). 
+For ECE ({{ece}}), ECK ({{eck}}), and self-managed clusters, AutoOps can be set up in all supported [regions](ec-autoops-regions.md#autoops-for-self-managed-clusters-regions) through [Cloud Connect](/deploy-manage/cloud-connect.md). More regions are coming soon.
 
 Cloud Connect enables users of ECE, ECK, and self-managed clusters to use {{ecloud}} services. This means you can take advantage of the simplified cluster monitoring, real-time issue detection, and performance recommendations of AutoOps without having to run and manage the underlying infrastructure.
 

@@ -23,7 +23,7 @@ $$$faq-what-is-autoops$$$What does AutoOps do?
 :   AutoOps for {{es}} significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, real-time issue detection and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs.
 
 $$$faq-autoops-deployment-types$$$Is AutoOps available in all types of deployments?
-:   In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+:   In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
 
 $$$faq-autoops-regions$$$Why can't I see AutoOps in some deployments?
 :   AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. 

@@ -11,7 +11,7 @@ navigation_title: For {{ech}}
 
 # AutoOps for {{ech}}
 
-For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon. 
+For [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) deployments, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon. 
 
 ## How to access AutoOps [ec-autoops-how-to-access]
 
@@ -20,7 +20,3 @@ To access AutoOps from your {{ecloud}} console, follow these steps:
 1. Log in to your {{ech}} account.
 2. Locate the deployment you want to work on and select **Manage**.
 4. On the deployment overview page, select **Open AutoOps**.
-
-:::{image} /deploy-manage/images/cloud-autoops-how-to-access.png
-:alt: How to access AutoOps
-:::
@@ -25,7 +25,7 @@ AutoOps is currently not available in any region for GovCloud customers.
 
 ## AutoOps for {{ECH}} regions
 
-AutoOps for {{ECH}} is currently available in the following regions for AWS:
+AutoOps for {{ECH}} is set up and enabled automatically in the following regions for AWS:
 
 | Region | Name |
 | --- | --- | --- | --- |
@@ -53,18 +53,11 @@ AutoOps for {{ECH}} is currently available in the following regions for AWS:
 
 Regions for Azure and GCP are coming soon.
 
-## AutoOps for self-managed clusters regions
-
-You can also use AutoOps with your ECE ({{ece}}), ECK ({{eck}}), or self-managed clusters through [Cloud Connect](/deploy-manage/cloud-connect.md). 
-
-This service is currently available in the following regions for AWS:
-
-:::{include} ../_snippets/autoops-cc-regions.md
-:::
+Learn how to [access](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) AutoOps in your {{ECH}} deployment.
 
 ## AutoOps for {{serverless-full}} regions
 
-AutoOps for serverless projects is currently available in the following regions for AWS:
+AutoOps for Serverless is set up and enabled automatically in the following regions for AWS:
 
 | Region | Name |
 | --- | --- | --- | --- |
@@ -73,4 +66,17 @@ AutoOps for serverless projects is currently available in the following regions
 | ap-southeast-1 | Asia Pacific (Singapore) |
 | us-west-2 | US West (Oregon) |
 
-The only exception is the **Search AI Lake** view, which is available in all CSP regions across AWS, Azure and GCP.
+The only exception is the **Search AI Lake** view, which is available in all CSP regions across AWS, Azure, and GCP.
+
+Learn how to [access](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) AutoOps in your serverless project.
+
+## AutoOps for self-managed clusters regions
+
+You can also use AutoOps with your ECE ({{ece}}), ECK ({{eck}}), or self-managed clusters through [Cloud Connect](/deploy-manage/cloud-connect.md). 
+
+This service is currently available in the following regions for AWS:
+
+:::{include} ../_snippets/autoops-cc-regions.md
+:::
+
+Learn how to [set up](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) AutoOps in your ECE, ECK, or self-managed cluster.