From 38d8f32ad0ac012d7b0157b0d89bba9c35fa3268 Mon Sep 17 00:00:00 2001 From: Marci W <333176+marciw@users.noreply.github.com> Date: Sun, 17 Nov 2024 11:15:02 -0500 Subject: [PATCH 1/8] Update pricing info; edit for style and clarity --- serverless/pages/ingest-your-data.asciidoc | 2 + .../manage-billing-monitor-usage.asciidoc | 17 ++---- serverless/pages/manage-your-project.asciidoc | 11 ++-- serverless/pages/pricing.asciidoc | 61 +++++++++---------- 4 files changed, 44 insertions(+), 47 deletions(-) diff --git a/serverless/pages/ingest-your-data.asciidoc b/serverless/pages/ingest-your-data.asciidoc index 8b538ad2..a1d360f5 100644 --- a/serverless/pages/ingest-your-data.asciidoc +++ b/serverless/pages/ingest-your-data.asciidoc @@ -24,6 +24,8 @@ This data can be updated, but the value of the content remains relatively consta Use connector clients to sync data from a range of popular data sources to {es}. You can also send data directly to {es} from your application using the API. +[discrete] +[[elasticsearch-ingest-time-series-data]] **Times series (timestamped) data** Time series, or timestamped data, describes data that changes frequently and "flows" over time, such as stock quotes, system metrics, and network traffic data. diff --git a/serverless/pages/manage-billing-monitor-usage.asciidoc b/serverless/pages/manage-billing-monitor-usage.asciidoc index 597c325f..5ff7f13e 100644 --- a/serverless/pages/manage-billing-monitor-usage.asciidoc +++ b/serverless/pages/manage-billing-monitor-usage.asciidoc @@ -6,23 +6,18 @@ preview:[] -To find more details about your account usage: +To get more details about your account usage: . Navigate to https://cloud.elastic.co/[cloud.elastic.co] and log in to your {ecloud} account. -. Go to the user icon on the header bar and select **Billing**. +. In the header bar, click the user icon, then select **Billing**. -On the **Usage** page you can: +On the **Usage** tab of the **Billing** page, you can: -* Monitor the usage for the current month, including total hourly rate and month-to-date usage +* Monitor usage for the current month, including month-to-date usage * Check the usage breakdown for a selected time range +* View usage totals by product [IMPORTANT] ==== The usage breakdown information is an estimate. To get the exact amount you owe for a given month, check your invoices in the <>. -==== - -.Elasticsearch minimum runtime VCUs -[IMPORTANT] -==== -When you create an Elasticsearch Serverless project, a minimum number of VCUs are always allocated to your project to maintain basic ingest and search capabilities. These VCUs incur a minimum cost even with no active usage. Learn more about https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless[minimum VCUs on Elasticsearch Serverless]. -==== +==== \ No newline at end of file diff --git a/serverless/pages/manage-your-project.asciidoc b/serverless/pages/manage-your-project.asciidoc index 7744ace3..06778328 100644 --- a/serverless/pages/manage-your-project.asciidoc +++ b/serverless/pages/manage-your-project.asciidoc @@ -34,17 +34,20 @@ The total volume of search-ready data is the sum of the following: Each project type offers different settings that let you adjust the performance and volume of search-ready data, as well as the features available in your projects. +[discrete] +[[elasticsearch-manage-project-search-power-settings]] |=== | Setting | Description | Available in | **Search Power** -a| Search Power affects search speed by controlling the number of VCUs (Virtual Compute Units) allocated to search-ready data in the project. Additional VCUs provide more compute resources and result in performance gains. +a| Search Power controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs. +Choose from three Search Power settings: -The **Cost-efficient** Search Power setting limits the available cache size, and generates cost savings by reducing search performance. +**On-demand:** Autoscales based on data and search load, with a lower minimum baseline for resource use. This flexibility results in more variable query latency and reduced maximum throughput. -The **Balanced** Search Power setting ensures that there is sufficient cache for all search-ready data, in order to respond quickly to queries. +**Performant:** Delivers consistently low latency and autoscales to accommodate moderately high query throughput. -The **Performance** Search Power setting provides more computing resources in addition to the searchable data cache, in order to respond quickly to higher query volumes and more complex queries. +**High-throughput:** Optimized for high-throughput scenarios, autoscaling to maintain query latency even at very high query volumes. | {es-badge} | **Search Boost Window** diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index 34a35d92..d39535ff 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -6,51 +6,48 @@ preview:[] -Elasticsearch is priced based on the consumption of the underlying -infrastructure used to support your use case, with the performance -characteristics you need. We measure by Virtual Compute Units (VCUs), which is a -slice of RAM, CPU and local disk for caching. The number of VCUs required will -depend on the amount and the rate of data sent to Elasticsearch and retained, -and the number of searches and latency you require for searches. In addition, if -you required {ml} for inference or NLP tasks, those VCUs are also +Elasticsearch is priced based on consumption of the underlying +infrastructure that supports your use case, with the performance +characteristics you need. Measurements are in Virtual Compute Units (VCUs). +Each VCU represents a slice of RAM, CPU, and local disk for caching. + +The number of VCUs required +depends on the amount and rate of data sent to Elasticsearch and retained, +as well as the number of searches and the latency you require for searches. In addition, if +you use {ml} for inference or NLP tasks, those VCUs are also metered and billed. -include::../partials/minimum-vcus-detail.asciidoc[] - [discrete] [[elasticsearch-billing-information-about-the-vcu-types-search-ingest-and-ml]] -== Information about the VCU types (Search, Ingest, and ML) +== VCU types: Search, Ingest, and ML -There are three VCU types in Elasticsearch: +Elasticsearch uses three VCU types: -* **Indexing** — The VCUs used to index the incoming documents to be -stored in Elasticsearch. -* **Search** — The VCUs used to return search results with the latency and -Queries per Second (QPS) you require. -* **Machine Learning** — The VCUs used to perform inference, NLP tasks, and other ML activities. +* **Indexing:** The VCUs used to index incoming documents. +* **Search:** The VCUs used to return search results, with the latency and +queries per second (QPS) you require. +* **Machine learning:** The VCUs used to perform inference, NLP tasks, and other ML activities. [discrete] [[elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]] -== Information about the Search AI Lake dimension (GB) +== Search AI Lake dimension (GB) -For Elasticsearch, the Search AI Lake is where data is stored and retained. This is -charged in GBs for the size of data at rest. Depending on the enrichment, -vectorization and other activities during ingest, this size may be different +Elasticsearch stores and retains data in the <>, +which is charged in GB for the size of data at rest. Depending on enrichment, +vectorization, and other activities during ingest, this size may be different from the original size of the source data. [discrete] [[elasticsearch-billing-managing-elasticsearch-costs]] == Managing Elasticsearch costs -You can control costs in a number of ways. Firstly there is the amount of -data that is retained. Elasticsearch will ensure that the most recent data is -cached, allowing for fast retrieval. Reducing the amount of data means fewer -Search VCUs may be required. If you need lower latency, then more Search VCUs -can be added by adjusting the Search Power. A further refinement is for data streams that can be used to store -time series data. For that type of data, you can further define the number of -days of data you want cacheable, which will affect the number of Search VCUs and -therefore the cost. Note that Elasticsearch Serverless maintains and bills for -https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless[minimum compute resource Ingest and Search VCUs]. - -For detailed Elasticsearch serverless project rates, check the -https://www.elastic.co/pricing/serverless-search[Elasticsearch Serverless pricing page]. +You can control costs by using a lower Search Power setting or reducing the amount +of retained data. + +* **Search Power setting:** <> controls the speed of searches against your data. With Search Power, you can +improve search performance by adding more resources for querying, or you can reduce provisioned +resources to cut costs. +* **Time series data:** By limiting the number of days of <> that are available for caching, +you can reduce the number of search VCUs required. + +For detailed {es-serverless} project rates, see the https://www.elastic.co/pricing/serverless-search[{es-serverless} pricing page]. From a38196344ac083c7ba4ab37005f81639c702639b Mon Sep 17 00:00:00 2001 From: George Wallace Date: Mon, 18 Nov 2024 11:54:53 -0700 Subject: [PATCH 2/8] Update serverless/pages/pricing.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --- serverless/pages/pricing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index d39535ff..d22bde45 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -9,7 +9,7 @@ preview:[] Elasticsearch is priced based on consumption of the underlying infrastructure that supports your use case, with the performance characteristics you need. Measurements are in Virtual Compute Units (VCUs). -Each VCU represents a slice of RAM, CPU, and local disk for caching. +Each VCU represents a fraction of RAM, CPU, and local disk for caching. The number of VCUs required depends on the amount and rate of data sent to Elasticsearch and retained, From 89d4321842474969ac0ae78a9d86e2a1ef58e35d Mon Sep 17 00:00:00 2001 From: George Wallace Date: Mon, 18 Nov 2024 11:55:04 -0700 Subject: [PATCH 3/8] Update serverless/pages/pricing.asciidoc Co-authored-by: florent-leborgne --- serverless/pages/pricing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index d22bde45..1da0c47f 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -47,7 +47,7 @@ of retained data. * **Search Power setting:** <> controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs. -* **Time series data:** By limiting the number of days of <> that are available for caching, +* **Time series data retention:** By limiting the number of days of <> that are available for caching, you can reduce the number of search VCUs required. For detailed {es-serverless} project rates, see the https://www.elastic.co/pricing/serverless-search[{es-serverless} pricing page]. From f43e6be1aca3c64df7b5cab0742be4b7d4ebf99a Mon Sep 17 00:00:00 2001 From: George Wallace Date: Mon, 18 Nov 2024 11:55:36 -0700 Subject: [PATCH 4/8] Update serverless/pages/pricing.asciidoc Co-authored-by: florent-leborgne --- serverless/pages/pricing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index 1da0c47f..b450934e 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -19,7 +19,7 @@ metered and billed. [discrete] [[elasticsearch-billing-information-about-the-vcu-types-search-ingest-and-ml]] -== VCU types: Search, Ingest, and ML +== VCU types: Search, Indexing, and ML Elasticsearch uses three VCU types: From d904065ae82c3c32b9cbadd5db37f1015fa4d141 Mon Sep 17 00:00:00 2001 From: George Wallace Date: Mon, 18 Nov 2024 11:57:12 -0700 Subject: [PATCH 5/8] Update serverless/pages/pricing.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --- serverless/pages/pricing.asciidoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index b450934e..f56f3f3e 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -32,10 +32,7 @@ queries per second (QPS) you require. [[elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]] == Search AI Lake dimension (GB) -Elasticsearch stores and retains data in the <>, -which is charged in GB for the size of data at rest. Depending on enrichment, -vectorization, and other activities during ingest, this size may be different -from the original size of the source data. +{es-serverless} projects store data in the <>. You are charged per GB of stored data at rest. Note that if you perform operations at ingest such as vectorization or enrichment, the size of your stored data will differ from the size of the original source data. [discrete] [[elasticsearch-billing-managing-elasticsearch-costs]] From 382301d746ff1f7e9085f8a9b3b766d26aedde10 Mon Sep 17 00:00:00 2001 From: George Wallace Date: Tue, 19 Nov 2024 16:01:10 -0700 Subject: [PATCH 6/8] Update serverless/pages/pricing.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --- serverless/pages/pricing.asciidoc | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index f56f3f3e..c37c5bae 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -11,11 +11,13 @@ infrastructure that supports your use case, with the performance characteristics you need. Measurements are in Virtual Compute Units (VCUs). Each VCU represents a fraction of RAM, CPU, and local disk for caching. -The number of VCUs required -depends on the amount and rate of data sent to Elasticsearch and retained, -as well as the number of searches and the latency you require for searches. In addition, if -you use {ml} for inference or NLP tasks, those VCUs are also -metered and billed. +The number of VCUs you need is determined by: + +* Volume and ingestion rate of your data +* Data retention requirements +* Search query volume +* Search Power setting +* Machine learning usage [discrete] [[elasticsearch-billing-information-about-the-vcu-types-search-ingest-and-ml]] From d11244f4a38366196637401d2017e04d284a246c Mon Sep 17 00:00:00 2001 From: George Wallace Date: Tue, 19 Nov 2024 16:01:25 -0700 Subject: [PATCH 7/8] Update serverless/pages/pricing.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --- serverless/pages/pricing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index c37c5bae..cfb669ea 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -32,7 +32,7 @@ queries per second (QPS) you require. [discrete] [[elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]] -== Search AI Lake dimension (GB) +== Data storage and billing {es-serverless} projects store data in the <>. You are charged per GB of stored data at rest. Note that if you perform operations at ingest such as vectorization or enrichment, the size of your stored data will differ from the size of the original source data. From c42343f0bd23c3481c9ef362d5dbc895636a2c97 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 20 Nov 2024 10:43:06 +0100 Subject: [PATCH 8/8] fix delimiter --- serverless/pages/manage-billing-monitor-usage.asciidoc | 1 + 1 file changed, 1 insertion(+) diff --git a/serverless/pages/manage-billing-monitor-usage.asciidoc b/serverless/pages/manage-billing-monitor-usage.asciidoc index e541ae92..21828b43 100644 --- a/serverless/pages/manage-billing-monitor-usage.asciidoc +++ b/serverless/pages/manage-billing-monitor-usage.asciidoc @@ -20,4 +20,5 @@ On the **Usage** tab of the **Billing** page, you can: [IMPORTANT] ==== The usage breakdown information is an estimate. To get the exact amount you owe for a given month, check your invoices in the <>. +====