diff --git a/serverless/index-serverless-elasticsearch.asciidoc b/serverless/index-serverless-elasticsearch.asciidoc index 80370e7..64d5302 100644 --- a/serverless/index-serverless-elasticsearch.asciidoc +++ b/serverless/index-serverless-elasticsearch.asciidoc @@ -5,6 +5,7 @@ ++++ include::./pages/what-is-elasticsearch-serverless.asciidoc[leveloffset=+2] +include::./pages/serverless-differences.asciidoc[leveloffset=+2] include::./pages/pricing.asciidoc[leveloffset=+2] @@ -42,8 +43,4 @@ include::./pages/search-your-data-semantic-search.asciidoc[leveloffset=+3] include::./pages/explore-your-data.asciidoc[leveloffset=+2] -include::./pages/search-playground.asciidoc[leveloffset=+2] - -include::./pages/serverless-differences.asciidoc[leveloffset=+2] - -include::./pages/technical-preview-limitations.asciidoc[leveloffset=+2] +include::./pages/search-playground.asciidoc[leveloffset=+2] \ No newline at end of file diff --git a/serverless/pages/action-connectors.asciidoc b/serverless/pages/action-connectors.asciidoc index 704627a..b921015 100644 --- a/serverless/pages/action-connectors.asciidoc +++ b/serverless/pages/action-connectors.asciidoc @@ -4,8 +4,6 @@ // :description: Configure connections to third party systems for use in cases and rules. // :keywords: serverless -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} The list of available connectors varies by project type. diff --git a/serverless/pages/api-keys.asciidoc b/serverless/pages/api-keys.asciidoc index 794f8c1..d3a1519 100644 --- a/serverless/pages/api-keys.asciidoc +++ b/serverless/pages/api-keys.asciidoc @@ -4,8 +4,6 @@ // :description: API keys allow access to the {stack} on behalf of a user. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} API keys are security mechanisms used to authenticate and authorize access to {stack} resources, diff --git a/serverless/pages/apis-elasticsearch-conventions.asciidoc b/serverless/pages/apis-elasticsearch-conventions.asciidoc index c23a9cc..4681854 100644 --- a/serverless/pages/apis-elasticsearch-conventions.asciidoc +++ b/serverless/pages/apis-elasticsearch-conventions.asciidoc @@ -4,8 +4,6 @@ // :description: The {es-serverless} REST APIs have conventions for headers and request bodies. // :keywords: serverless, elasticsearch, API, reference -preview:[] - You can run {es} API requests in **{dev-tools-app} → Console**. For example: diff --git a/serverless/pages/apis-http-apis.asciidoc b/serverless/pages/apis-http-apis.asciidoc index 937744c..8de2a62 100644 --- a/serverless/pages/apis-http-apis.asciidoc +++ b/serverless/pages/apis-http-apis.asciidoc @@ -4,8 +4,33 @@ // :description: {es} and {kib} expose REST APIs that can be called directly to configure and access {stack} features. // :keywords: serverless, elasticsearch, http, rest, overview -preview:[] +[discrete] +[[elasticsearch-api-references-links]] +== API references -* <>: The {es-serverless} REST APIs have conventions for headers and request bodies. -* <>: The Management APIs for {serverless-short} have request header conventions. -* https://www.elastic.co/docs/api/[API Reference]: Explore the reference information for Elastic Serverless REST APIs +The following APIs are available for {es-serverless} users. +These links will take you to the autogenerated API reference documentation. + +https://www.elastic.co/docs/api/doc/elasticsearch-serverless[Elasticsearch Serverless APIs →]:: +Use these APIs to index, manage, search, and analyze your data in {es-serverless}. ++ +[TIP] +==== +Learn how to <>. +==== + +https://www.elastic.co/docs/api/doc/serverless[Kibana Serverless APIs →]:: +Use these APIs to manage resources such as connectors, data views, and saved objects for your {serverless-full} project. + +https://www.elastic.co/docs/api/doc/elastic-cloud-serverless[{serverless-full} APIs →]:: +Use these APIs to manage your {serverless-full} projects. + +[discrete] +[[additional-api-details]] +== Additional API information + +<>:: +Reference information about headers and request body conventions for {es-serverless} REST APIs. + +<>:: +Reference information about request header conventions for {serverless-full} REST APIs. diff --git a/serverless/pages/apis-kibana-conventions.asciidoc b/serverless/pages/apis-kibana-conventions.asciidoc index 5e47fbb..926ae6a 100644 --- a/serverless/pages/apis-kibana-conventions.asciidoc +++ b/serverless/pages/apis-kibana-conventions.asciidoc @@ -4,8 +4,6 @@ // :description: The Management APIs for {serverless-short} have request header conventions. // :keywords: serverless, kibana, API, reference -preview:[] - The Management REST APIs for {serverless-full} let you manage resources that are available in multiple solutions. These resources include connectors, data views, and saved objects. If you've previously used the {stack}, the Management APIs are similar to {kib} APIs. diff --git a/serverless/pages/clients-dot-net-getting-started.asciidoc b/serverless/pages/clients-dot-net-getting-started.asciidoc index 4697b03..1f9ab78 100644 --- a/serverless/pages/clients-dot-net-getting-started.asciidoc +++ b/serverless/pages/clients-dot-net-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the .NET client for {es3}. // :keywords: serverless, elasticsearch, .net, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-go-getting-started.asciidoc b/serverless/pages/clients-go-getting-started.asciidoc index 33caeaf..60764b3 100644 --- a/serverless/pages/clients-go-getting-started.asciidoc +++ b/serverless/pages/clients-go-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the Go client for {es3}. // :keywords: serverless, elasticsearch, go, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-java-getting-started.asciidoc b/serverless/pages/clients-java-getting-started.asciidoc index c6640d6..acb7f34 100644 --- a/serverless/pages/clients-java-getting-started.asciidoc +++ b/serverless/pages/clients-java-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the Java client for {es3}. // :keywords: serverless, elasticsearch, java, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-nodejs-getting-started.asciidoc b/serverless/pages/clients-nodejs-getting-started.asciidoc index 4e0b1db..d4c57d0 100644 --- a/serverless/pages/clients-nodejs-getting-started.asciidoc +++ b/serverless/pages/clients-nodejs-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the Node.js client for {es3}. // :keywords: serverless, elasticsearch, nodejs, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-php-getting-started.asciidoc b/serverless/pages/clients-php-getting-started.asciidoc index 7cc42c4..87522d2 100644 --- a/serverless/pages/clients-php-getting-started.asciidoc +++ b/serverless/pages/clients-php-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the PHP client for {es3}. // :keywords: serverless, elasticsearch, php, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-python-getting-started.asciidoc b/serverless/pages/clients-python-getting-started.asciidoc index 9dee1a4..8f12342 100644 --- a/serverless/pages/clients-python-getting-started.asciidoc +++ b/serverless/pages/clients-python-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the Python client for {es3}. // :keywords: serverless, elasticsearch, python, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients-ruby-getting-started.asciidoc b/serverless/pages/clients-ruby-getting-started.asciidoc index 6f18fbb..f715539 100644 --- a/serverless/pages/clients-ruby-getting-started.asciidoc +++ b/serverless/pages/clients-ruby-getting-started.asciidoc @@ -4,8 +4,6 @@ // :description: Set up and use the Ruby client for {es3}. // :keywords: serverless, elasticsearch, ruby, how to -preview:[] - [NOTE] ==== This client is for use with {es-serverless} only. See also the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} clients]. diff --git a/serverless/pages/clients.asciidoc b/serverless/pages/clients.asciidoc index e3c426c..9590ed2 100644 --- a/serverless/pages/clients.asciidoc +++ b/serverless/pages/clients.asciidoc @@ -4,8 +4,6 @@ // :description: Index, search, and manage {es} data in your preferred language. // :keywords: serverless, elasticsearch, clients, overview -preview:[] - {es3} provides official language clients for {es} REST APIs. [NOTE] @@ -22,3 +20,8 @@ Currently, the following language clients are supported: * <> | https://github.com/elastic/elasticsearch-serverless-php[Repository] * <> | https://github.com/elastic/elasticsearch-serverless-python[Repository] * <> | https://github.com/elastic/elasticsearch-serverless-ruby[Repository] + +[TIP] +==== +Learn how to <>. +==== diff --git a/serverless/pages/connecting-to-es-endpoint.asciidoc b/serverless/pages/connecting-to-es-endpoint.asciidoc index 02069ee..3474623 100644 --- a/serverless/pages/connecting-to-es-endpoint.asciidoc +++ b/serverless/pages/connecting-to-es-endpoint.asciidoc @@ -1,5 +1,8 @@ [[elasticsearch-connecting-to-es-serverless-endpoint]] -= Connecting to your Elasticsearch Serverless endpoint += Connect to your Elasticsearch Serverless endpoint +++++ +Connect to your endpoint +++++ [TIP] ==== diff --git a/serverless/pages/custom-roles.asciidoc b/serverless/pages/custom-roles.asciidoc index 041205c..57f3c80 100644 --- a/serverless/pages/custom-roles.asciidoc +++ b/serverless/pages/custom-roles.asciidoc @@ -9,7 +9,6 @@ coming:[] endif::[] ifdef::serverlessCustomRoles[] -preview:[] This content applies to: {es-badge} {sec-badge} diff --git a/serverless/pages/data-views.asciidoc b/serverless/pages/data-views.asciidoc index 4576989..bfa31dc 100644 --- a/serverless/pages/data-views.asciidoc +++ b/serverless/pages/data-views.asciidoc @@ -4,8 +4,6 @@ // :description: Elastic requires a {data-source} to access the {es} data that you want to explore. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} A {data-source} can point to one or more indices, {ref}/data-streams.html[data streams], or {ref}/alias.html[index aliases]. diff --git a/serverless/pages/debug-grok-expressions.asciidoc b/serverless/pages/debug-grok-expressions.asciidoc index df257d9..ad0dc75 100644 --- a/serverless/pages/debug-grok-expressions.asciidoc +++ b/serverless/pages/debug-grok-expressions.asciidoc @@ -4,8 +4,6 @@ // :description: Build and debug grok patterns before you use them in your data processing pipelines. // :keywords: serverless, dev tools, how-to -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} You can build and debug grok patterns in the **Grok Debugger** before you use them in your data processing pipelines. @@ -43,7 +41,7 @@ The **Admin** role is required to use the Grok Debugger. For more information, refer to <> ==== -. From the main menu, click **Developer Tools**, then click **Grok Debugger**. +. In the main menu, go to **Developer Tools** under *Build*, then click **Grok Debugger**. . In **Sample Data**, enter a message that is representative of the data you want to parse. For example: + diff --git a/serverless/pages/debug-painless-scripts.asciidoc b/serverless/pages/debug-painless-scripts.asciidoc index 045aaaa..262cc25 100644 --- a/serverless/pages/debug-painless-scripts.asciidoc +++ b/serverless/pages/debug-painless-scripts.asciidoc @@ -4,8 +4,6 @@ // :description: Use our interactive code editor to test and debug Painless scripts in real-time. // :keywords: serverless, dev tools, how-to -preview:[] - This content applies to: {obs-badge} {sec-badge} beta::[] diff --git a/serverless/pages/developer-tools-troubleshooting.asciidoc b/serverless/pages/developer-tools-troubleshooting.asciidoc index 65fcff9..0a883ca 100644 --- a/serverless/pages/developer-tools-troubleshooting.asciidoc +++ b/serverless/pages/developer-tools-troubleshooting.asciidoc @@ -4,8 +4,6 @@ // :description: Troubleshoot searches. // :keywords: serverless, troubleshooting -preview:[] - When you query your data, {es} may return an error, no search results, or results in an unexpected order. This guide describes how to troubleshoot searches. diff --git a/serverless/pages/elasticsearch-developer-tools.asciidoc b/serverless/pages/elasticsearch-developer-tools.asciidoc index 76e8f23..6386c42 100644 --- a/serverless/pages/elasticsearch-developer-tools.asciidoc +++ b/serverless/pages/elasticsearch-developer-tools.asciidoc @@ -4,8 +4,6 @@ // :description: Elastic tools for developers. // :keywords: serverless, elasticsearch, overview -preview:[] - A number of developer tools are available in your project's UI under the **Dev Tools** section. * <>: Make API calls to your {es} instance using the Query DSL and view the responses. diff --git a/serverless/pages/explore-your-data-ml-nlp-classify-text.asciidoc b/serverless/pages/explore-your-data-ml-nlp-classify-text.asciidoc index e4928c9..346872d 100644 --- a/serverless/pages/explore-your-data-ml-nlp-classify-text.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-classify-text.asciidoc @@ -3,8 +3,6 @@ // :description: NLP tasks that classify input text or determine the language of text. // :keywords: serverless, elasticsearch, tbd -preview:[] - These NLP tasks enable you to identify the language of text and classify or label unstructured input text: diff --git a/serverless/pages/explore-your-data-ml-nlp-deploy-model.asciidoc b/serverless/pages/explore-your-data-ml-nlp-deploy-model.asciidoc index c45fae6..6f24c54 100644 --- a/serverless/pages/explore-your-data-ml-nlp-deploy-model.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-deploy-model.asciidoc @@ -2,8 +2,6 @@ // :description: Description to be written -preview:[] - After you import the model and vocabulary, you can use {kib} to view and manage their deployment across your cluster under **{ml-app}** → **Model Management**. Alternatively, you can use the diff --git a/serverless/pages/explore-your-data-ml-nlp-deploy-trained-models.asciidoc b/serverless/pages/explore-your-data-ml-nlp-deploy-trained-models.asciidoc index e4fc0a8..90346ee 100644 --- a/serverless/pages/explore-your-data-ml-nlp-deploy-trained-models.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-deploy-trained-models.asciidoc @@ -3,8 +3,6 @@ // :description: You can import trained models into your cluster and configure them for specific NLP tasks. // :keywords: serverless, elasticsearch, tbd -preview:[] - If you want to perform {nlp} tasks in your cluster, you must deploy an appropriate trained model. There is tooling support in https://github.com/elastic/eland[Eland] and {kib} to help you prepare and diff --git a/serverless/pages/explore-your-data-ml-nlp-elser.asciidoc b/serverless/pages/explore-your-data-ml-nlp-elser.asciidoc index ef2312d..32a026f 100644 --- a/serverless/pages/explore-your-data-ml-nlp-elser.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-elser.asciidoc @@ -3,8 +3,6 @@ // :description: ELSER is a learned sparse ranking model trained by Elastic. // :keywords: serverless, elasticsearch, tbd -preview:[] - Elastic Learned Sparse EncodeR - or ELSER - is a retrieval model trained by Elastic that enables you to perform {ref}/semantic-search-elser.html[semantic search] to retrieve more relevant diff --git a/serverless/pages/explore-your-data-ml-nlp-examples.asciidoc b/serverless/pages/explore-your-data-ml-nlp-examples.asciidoc index 304d9c4..991fd10 100644 --- a/serverless/pages/explore-your-data-ml-nlp-examples.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-examples.asciidoc @@ -2,8 +2,6 @@ // :description: Description to be written -preview:[] - The following pages contain end-to-end examples of how to use the different {nlp} tasks in the {stack}. diff --git a/serverless/pages/explore-your-data-ml-nlp-extract-info.asciidoc b/serverless/pages/explore-your-data-ml-nlp-extract-info.asciidoc index 80cfb8c..03f7786 100644 --- a/serverless/pages/explore-your-data-ml-nlp-extract-info.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-extract-info.asciidoc @@ -3,8 +3,6 @@ // :description: NLP tasks that extract information from unstructured text. // :keywords: serverless, elasticsearch, tbd -preview:[] - These NLP tasks enable you to extract information from your unstructured text: * https://www.elastic.co/docs/current/serverless/elasticsearch/explore-your-data-ml-nlp/extract-info[Named entity recognition] diff --git a/serverless/pages/explore-your-data-ml-nlp-import-model.asciidoc b/serverless/pages/explore-your-data-ml-nlp-import-model.asciidoc index 4588724..2fc9bba 100644 --- a/serverless/pages/explore-your-data-ml-nlp-import-model.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-import-model.asciidoc @@ -2,8 +2,6 @@ // :keywords: serverless, elasticsearch, tbd -preview:[] - [IMPORTANT] ==== If you want to install a trained model in a restricted or closed diff --git a/serverless/pages/explore-your-data-ml-nlp-inference.asciidoc b/serverless/pages/explore-your-data-ml-nlp-inference.asciidoc index 6095f0c..bd8b3cd 100644 --- a/serverless/pages/explore-your-data-ml-nlp-inference.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-inference.asciidoc @@ -3,8 +3,6 @@ // :description: You can import trained models into your cluster and configure them for specific NLP tasks. // :keywords: serverless, elasticsearch, tbd -preview:[] - After you https://www.elastic.co/docs/current/serverless/elasticsearch/explore-your-data-ml-nlp/deploy-trained-models[deploy a trained model in your cluster], you can use it to perform {nlp} tasks in ingest pipelines. diff --git a/serverless/pages/explore-your-data-ml-nlp-lang-ident.asciidoc b/serverless/pages/explore-your-data-ml-nlp-lang-ident.asciidoc index e389d91..08c967b 100644 --- a/serverless/pages/explore-your-data-ml-nlp-lang-ident.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-lang-ident.asciidoc @@ -3,8 +3,6 @@ // :description: Language identification is an NLP task and a model that enables you to determine the language of text. // :keywords: serverless, elasticsearch, tbd -preview:[] - {lang-ident-cap} enables you to determine the language of text. A {lang-ident} model is provided in your cluster, which you can use in an diff --git a/serverless/pages/explore-your-data-ml-nlp-model-ref.asciidoc b/serverless/pages/explore-your-data-ml-nlp-model-ref.asciidoc index 17a1099..5c38de5 100644 --- a/serverless/pages/explore-your-data-ml-nlp-model-ref.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-model-ref.asciidoc @@ -3,8 +3,6 @@ // :description: The list of compatible third party NLP models. // :keywords: ml, reference, analyze -preview:[] - The {stack-ml-features} support transformer models that conform to the standard BERT model interface and use the WordPiece tokenization algorithm. diff --git a/serverless/pages/explore-your-data-ml-nlp-ner-example.asciidoc b/serverless/pages/explore-your-data-ml-nlp-ner-example.asciidoc index 3543d8d..03cd5ce 100644 --- a/serverless/pages/explore-your-data-ml-nlp-ner-example.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-ner-example.asciidoc @@ -2,8 +2,6 @@ // :description: Description to be written -preview:[] - You can use these instructions to deploy a https://www.elastic.co/docs/current/serverless/elasticsearch/explore-your-data-ml-nlp/extract-info[named entity recognition (NER)] model in {es}, test the model, and add it to an {infer} ingest pipeline. The diff --git a/serverless/pages/explore-your-data-ml-nlp-ootb-models.asciidoc b/serverless/pages/explore-your-data-ml-nlp-ootb-models.asciidoc index 5f0713a..f452a56 100644 --- a/serverless/pages/explore-your-data-ml-nlp-ootb-models.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-ootb-models.asciidoc @@ -3,8 +3,6 @@ // :description: Models trained and provided by Elastic // :keywords: serverless, elasticsearch, tbd -preview:[] - You can use models that are trained and provided by Elastic that are available within the {stack} with a click of a button. diff --git a/serverless/pages/explore-your-data-ml-nlp-search-compare.asciidoc b/serverless/pages/explore-your-data-ml-nlp-search-compare.asciidoc index 0b16c7c..9773007 100644 --- a/serverless/pages/explore-your-data-ml-nlp-search-compare.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-search-compare.asciidoc @@ -3,8 +3,6 @@ // :description: NLP tasks for generate embeddings which can be used to search in text or compare different peieces of text. // :keywords: serverless, elasticsearch, tbd -preview:[] - The {stack-ml-features} can generate embeddings, which you can use to search in unstructured text or compare different pieces of text. diff --git a/serverless/pages/explore-your-data-ml-nlp-select-model.asciidoc b/serverless/pages/explore-your-data-ml-nlp-select-model.asciidoc index b02dafa..00a6b6a 100644 --- a/serverless/pages/explore-your-data-ml-nlp-select-model.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-select-model.asciidoc @@ -2,8 +2,6 @@ // :keywords: serverless, elasticsearch, tbd -preview:[] - Per the <>, there are multiple ways that you can use NLP features within the {stack}. diff --git a/serverless/pages/explore-your-data-ml-nlp-test-inference.asciidoc b/serverless/pages/explore-your-data-ml-nlp-test-inference.asciidoc index 39f93ff..4cd1b72 100644 --- a/serverless/pages/explore-your-data-ml-nlp-test-inference.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-test-inference.asciidoc @@ -3,8 +3,6 @@ // :description: You can import trained models into your cluster and configure them for specific NLP tasks. // :keywords: serverless, elasticsearch, tbd -preview:[] - When the model is deployed on at least one node in the cluster, you can begin to perform inference. _{infer-cap}_ is a {ml} feature that enables you to use your trained models to perform NLP tasks (such as text extraction, diff --git a/serverless/pages/explore-your-data-ml-nlp-text-embedding-example.asciidoc b/serverless/pages/explore-your-data-ml-nlp-text-embedding-example.asciidoc index 2fede73..a581f8d 100644 --- a/serverless/pages/explore-your-data-ml-nlp-text-embedding-example.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp-text-embedding-example.asciidoc @@ -2,8 +2,6 @@ // :description: Description to be written -preview:[] - You can use these instructions to deploy a https://www.elastic.co/docs/current/serverless/elasticsearch/explore-your-data-ml-nlp/search-compare-text[text embedding] model in {es}, test the model, and add it to an {infer} ingest pipeline. It diff --git a/serverless/pages/explore-your-data-ml-nlp.asciidoc b/serverless/pages/explore-your-data-ml-nlp.asciidoc index d655cd4..8fe9e94 100644 --- a/serverless/pages/explore-your-data-ml-nlp.asciidoc +++ b/serverless/pages/explore-your-data-ml-nlp.asciidoc @@ -2,8 +2,6 @@ // :keywords: serverless, elasticsearch, tbd -preview:[] - {nlp-cap} (NLP) refers to the way in which we can use software to understand natural language in spoken word or written text. diff --git a/serverless/pages/explore-your-data.asciidoc b/serverless/pages/explore-your-data.asciidoc index a9b8229..b274f11 100644 --- a/serverless/pages/explore-your-data.asciidoc +++ b/serverless/pages/explore-your-data.asciidoc @@ -4,9 +4,7 @@ // :description: Turn {es} data into actionable insights with aggregations, visualizations, and alerts // :keywords: serverless, elasticsearch, explore, overview -preview:[] - -In addition to search, {es-serverless} offers several options for analyzing and visualizing your data. +In addition to search, {es3} offers several options for analyzing and visualizing your data. [NOTE] ==== diff --git a/serverless/pages/files.asciidoc b/serverless/pages/files.asciidoc index c0716e8..bcd148a 100644 --- a/serverless/pages/files.asciidoc +++ b/serverless/pages/files.asciidoc @@ -4,8 +4,6 @@ // :description: Manage files that are stored in Elastic. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} Several {serverless-full} features let you upload files. For example, you can add files to <> or upload a logo to an **Image** panel in a {kibana-ref}/dashboard.html[Dashboard]. diff --git a/serverless/pages/fleet-and-elastic-agent.asciidoc b/serverless/pages/fleet-and-elastic-agent.asciidoc index ae57b48..69f59b7 100644 --- a/serverless/pages/fleet-and-elastic-agent.asciidoc +++ b/serverless/pages/fleet-and-elastic-agent.asciidoc @@ -4,8 +4,6 @@ // :description: Centrally manage your Elastic Agents in Fleet // :keywords: serverless, ingest, fleet, elastic agent -preview:[] - This content applies to: {obs-badge} {sec-badge} {agent} is a single, unified way to add monitoring for logs, metrics, and other types of data to a host. diff --git a/serverless/pages/general-developer-tools.asciidoc b/serverless/pages/general-developer-tools.asciidoc index 02e4f84..23be484 100644 --- a/serverless/pages/general-developer-tools.asciidoc +++ b/serverless/pages/general-developer-tools.asciidoc @@ -1,8 +1,6 @@ // :description: Use our developer tools to interact with your data. // :keywords: serverless, dev tools, overview -preview:[] - |=== | Feature | Description | Available in diff --git a/serverless/pages/get-started.asciidoc b/serverless/pages/get-started.asciidoc index 8acd015..dab32e2 100644 --- a/serverless/pages/get-started.asciidoc +++ b/serverless/pages/get-started.asciidoc @@ -4,8 +4,6 @@ // :description: Get started with {es3} in a few steps // :keywords: serverless, elasticsearch, getstarted, overview -preview:[] - On this page, you will learn how to: - <>. diff --git a/serverless/pages/index-management.asciidoc b/serverless/pages/index-management.asciidoc index 23a3f8e..0d58b56 100644 --- a/serverless/pages/index-management.asciidoc +++ b/serverless/pages/index-management.asciidoc @@ -4,8 +4,6 @@ // :description: Perform CRUD operations on indices and data streams. View index settings, mappings, and statistics. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} Elastic's index management features are an easy, convenient way to manage your cluster's indices, data streams, index templates, and enrich policies. diff --git a/serverless/pages/ingest-pipelines.asciidoc b/serverless/pages/ingest-pipelines.asciidoc index 6994372..da743d4 100644 --- a/serverless/pages/ingest-pipelines.asciidoc +++ b/serverless/pages/ingest-pipelines.asciidoc @@ -4,8 +4,6 @@ // :description: Create and manage {ingest-pipelines} to perform common transformations and enrichments on your data. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} {ref}/ingest.html[{ingest-pipelines-cap}] let you perform common transformations on your data before indexing. diff --git a/serverless/pages/ingest-your-data-ingest-data-through-api.asciidoc b/serverless/pages/ingest-your-data-ingest-data-through-api.asciidoc index da8389f..78a14b9 100644 --- a/serverless/pages/ingest-your-data-ingest-data-through-api.asciidoc +++ b/serverless/pages/ingest-your-data-ingest-data-through-api.asciidoc @@ -4,8 +4,6 @@ // :description: Add data to {es} using HTTP APIs or a language client. // :keywords: serverless, elasticsearch, ingest, api, how to -preview:[] - The {es} APIs enable you to ingest data through code. You can use the APIs of one of the <> or the diff --git a/serverless/pages/ingest-your-data-ingest-data-through-integrations-beats.asciidoc b/serverless/pages/ingest-your-data-ingest-data-through-integrations-beats.asciidoc index 9c80a9c..15d2b8c 100644 --- a/serverless/pages/ingest-your-data-ingest-data-through-integrations-beats.asciidoc +++ b/serverless/pages/ingest-your-data-ingest-data-through-integrations-beats.asciidoc @@ -4,8 +4,6 @@ // :description: Use {beats} to ship operational data to {es}. // :keywords: serverless, elasticsearch, ingest, beats, how to -preview:[] - {beats} are lightweight data shippers that send operational data to {es}. Elastic provides separate {beats} for different types of data, such as logs, metrics, and uptime. Depending on what data you want to collect, you may need to install multiple shippers on a single host. @@ -19,9 +17,6 @@ Depending on what data you want to collect, you may need to install multiple shi | Log files and journals | https://www.elastic.co/products/beats/filebeat[Filebeat] -| Cloud data -| https://www.elastic.co/products/beats/functionbeat[Functionbeat] - | Availability | https://www.elastic.co/products/beats/heartbeat[Heartbeat] diff --git a/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc b/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc index d2c109b..63640a7 100644 --- a/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc +++ b/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc @@ -4,8 +4,6 @@ // :description: Use {ls} to ship data to {es}. // :keywords: serverless, elasticsearch, ingest, logstash, how to -preview:[] - {ls} is an open source data collection engine with real-time pipelining capabilities. It supports a wide variety of data sources, and can dynamically unify data from disparate sources and normalize the data into destinations of your choice. @@ -21,7 +19,7 @@ such as data routed to multiple destinations or when you need to make your data {ls} is a powerful, versatile ETL (Extract, Transform, Load) engine that can play an important role in organizations of all sizes. Some capabilities and features for large, self-managed users aren't appropriate for {serverless-short}. -You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[`((es)) output plugin`] to send data to {es3}. +You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[{es} output plugin] to send data to {es3}. Some differences to note between {es3} and self-managed {es}: * Your logstash-output-elasticsearch configuration uses **API keys** to access {es} from {ls}. diff --git a/serverless/pages/ingest-your-data-upload-file.asciidoc b/serverless/pages/ingest-your-data-upload-file.asciidoc index 5520564..4c4bfeb 100644 --- a/serverless/pages/ingest-your-data-upload-file.asciidoc +++ b/serverless/pages/ingest-your-data-upload-file.asciidoc @@ -4,8 +4,6 @@ // :description: Add data to {es} using the File Uploader. // :keywords: serverless, elasticsearch, ingest, how to -preview:[] - You can upload files to {es} using the File Uploader. Use the visualizer to inspect the data before importing it. diff --git a/serverless/pages/ingest-your-data.asciidoc b/serverless/pages/ingest-your-data.asciidoc index 8880999..067b3b9 100644 --- a/serverless/pages/ingest-your-data.asciidoc +++ b/serverless/pages/ingest-your-data.asciidoc @@ -4,27 +4,36 @@ // :description: Add data to your {es-serverless} project. // :keywords: serverless, elasticsearch, ingest, overview -preview:[] +The best ingest option(s) for your use case depends on whether you are indexing general content or time series (timestamped) data. -You have many options for ingesting, or indexing, data into {es}: +[discrete] +[[es-ingestion-overview-apis]] +== Ingest data using APIs -* <> -* <> -* <> -* <> -* <> -* https://github.com/elastic/crawler[Elastic Open Web Crawler] +You can use the <> to add data to your {es} indices, using any HTTP client, including the <>. -The best ingest option(s) for your use case depends on whether you are indexing general content or time series (timestamped) data. +While the {es} APIs can be used for any data type, Elastic provides specialized tools that optimize ingestion for specific use cases. + +[discrete] +[[es-ingestion-overview-general-content]] +== Ingest general content -**General content** +General content is typically text-heavy data that does not have a timestamp. +This could be data like knowledge bases, website content, product catalogs, and more. -General content includes HTML pages, catalogs, files, and other content that does not update continuously. -This data can be updated, but the value of the content remains relatively constant over time. -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. +You can use these specialized tools to add general content to {es} indices: -**Times series (timestamped) data** +* <> +* https://github.com/elastic/crawler[Elastic Open Web Crawler] +* <> + +[discrete] +[[elasticsearch-ingest-time-series-data]] +== Ingest time series 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. -Use {beats} or {ls} to collect time series data. + +You can use these specialized tools to add timestamped data to {es} data streams: + +* <> +* <> diff --git a/serverless/pages/integrations.asciidoc b/serverless/pages/integrations.asciidoc index 8b4425b..8236017 100644 --- a/serverless/pages/integrations.asciidoc +++ b/serverless/pages/integrations.asciidoc @@ -4,8 +4,6 @@ // :description: Use our pre-built integrations to connect your data to Elastic. // :keywords: serverless, ingest, integration -preview:[] - This content applies to: {obs-badge} {sec-badge} Elastic integrations are a streamlined way to connect your data to Elastic. diff --git a/serverless/pages/knn-search.asciidoc b/serverless/pages/knn-search.asciidoc index ba2ade2..0db335b 100644 --- a/serverless/pages/knn-search.asciidoc +++ b/serverless/pages/knn-search.asciidoc @@ -4,8 +4,6 @@ // :description: Vector search with k-nearest neighbor (kNN). // :keywords: serverless, elasticsearch, search, vector, knn, ann -preview:[] - A _k-nearest neighbor_ (kNN) search finds the _k_ nearest vectors to a query vector, as measured by a similarity metric. diff --git a/serverless/pages/logstash-pipelines.asciidoc b/serverless/pages/logstash-pipelines.asciidoc index 7f2551c..5a44ffd 100644 --- a/serverless/pages/logstash-pipelines.asciidoc +++ b/serverless/pages/logstash-pipelines.asciidoc @@ -4,8 +4,6 @@ // :description: Create, edit, and delete your {ls} pipeline configurations. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} In **{project-settings} → {manage-app} → {ls-pipelines-app}**, you can control multiple {ls} instances and pipeline configurations. diff --git a/serverless/pages/machine-learning.asciidoc b/serverless/pages/machine-learning.asciidoc index 5462e27..5dba785 100644 --- a/serverless/pages/machine-learning.asciidoc +++ b/serverless/pages/machine-learning.asciidoc @@ -4,8 +4,6 @@ // :description: View, export, and import {ml} jobs and models. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} To view your {ml} resources, go to **{project-settings} → {manage-app} → {ml-app}**: diff --git a/serverless/pages/maintenance-windows.asciidoc b/serverless/pages/maintenance-windows.asciidoc index 38d0eb3..525dd59 100644 --- a/serverless/pages/maintenance-windows.asciidoc +++ b/serverless/pages/maintenance-windows.asciidoc @@ -4,8 +4,6 @@ // :description: Suppress rule notifications for scheduled periods of time. // :keywords: serverless, Observability, Security -preview:[] - This content applies to: {obs-badge} {sec-badge} preview::[] diff --git a/serverless/pages/manage-access-to-org-from-existing-account.asciidoc b/serverless/pages/manage-access-to-org-from-existing-account.asciidoc index 20607b9..fd5ec2f 100644 --- a/serverless/pages/manage-access-to-org-from-existing-account.asciidoc +++ b/serverless/pages/manage-access-to-org-from-existing-account.asciidoc @@ -4,8 +4,6 @@ // :description: Join a new organization and bring over your projects. // :keywords: serverless, general, organization, join, how to -preview:[] - If you already belong to an organization, and you want to join a new one, it is currently not possible to bring your projects over to the new organization. If you want to join a new project, follow these steps: diff --git a/serverless/pages/manage-access-to-org-user-roles.asciidoc b/serverless/pages/manage-access-to-org-user-roles.asciidoc index 6569c15..9463d83 100644 --- a/serverless/pages/manage-access-to-org-user-roles.asciidoc +++ b/serverless/pages/manage-access-to-org-user-roles.asciidoc @@ -4,8 +4,6 @@ // :description: Manage the predefined set of roles and privileges for all your projects. // :keywords: serverless, general, organization, roles, how to -preview:[] - Within an organization, users can have one or more roles and each role grants specific privileges. You must assign user roles when you <>. diff --git a/serverless/pages/manage-billing-check-subscription.asciidoc b/serverless/pages/manage-billing-check-subscription.asciidoc index fe61ee1..920cb28 100644 --- a/serverless/pages/manage-billing-check-subscription.asciidoc +++ b/serverless/pages/manage-billing-check-subscription.asciidoc @@ -4,8 +4,6 @@ // :description: Manage your account details and subscription level. // :keywords: serverless, general, billing, subscription -preview:[] - To find more details about your subscription: . Navigate to https://cloud.elastic.co/[cloud.elastic.co] and log in to your Elastic Cloud account. diff --git a/serverless/pages/manage-billing-history.asciidoc b/serverless/pages/manage-billing-history.asciidoc index d65f3d5..ec43f6b 100644 --- a/serverless/pages/manage-billing-history.asciidoc +++ b/serverless/pages/manage-billing-history.asciidoc @@ -4,8 +4,6 @@ // :description: Monitor payments and billing receipts. // :keywords: serverless, general, billing, history -preview:[] - Information about outstanding payments and billing receipts is available from the {ess-console}[{ess-console-name}]. To check your billing history: diff --git a/serverless/pages/manage-billing-monitor-usage.asciidoc b/serverless/pages/manage-billing-monitor-usage.asciidoc index b0add3f..8803d1f 100644 --- a/serverless/pages/manage-billing-monitor-usage.asciidoc +++ b/serverless/pages/manage-billing-monitor-usage.asciidoc @@ -4,25 +4,19 @@ // :description: Check the usage breakdown of your account. // :keywords: serverless, general, billing, usage -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 <>. ==== -.{es} minimum runtime VCUs -[IMPORTANT] -==== -When you create an {es-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 {es-serverless}]. -==== diff --git a/serverless/pages/manage-billing-pricing-model.asciidoc b/serverless/pages/manage-billing-pricing-model.asciidoc index 5dfd818..273ea4d 100644 --- a/serverless/pages/manage-billing-pricing-model.asciidoc +++ b/serverless/pages/manage-billing-pricing-model.asciidoc @@ -4,8 +4,6 @@ // :description: Understand how usage affects serverless pricing. // :keywords: serverless, general, billing, pricing model -preview:[] - Elastic Cloud serverless billing is based on your usage across these dimensions: * <> diff --git a/serverless/pages/manage-billing-stop-project.asciidoc b/serverless/pages/manage-billing-stop-project.asciidoc index 6500ac3..4fad387 100644 --- a/serverless/pages/manage-billing-stop-project.asciidoc +++ b/serverless/pages/manage-billing-stop-project.asciidoc @@ -4,8 +4,6 @@ // :description: How to stop charges for a project. // :keywords: serverless, general, billing -preview:[] - Got a project you no longer need and don't want to be charged for? Simply delete it. Warning: All data is lost. Billing for usage is by the hour and any outstanding charges for usage before you deleted the project will still appear on your next bill. diff --git a/serverless/pages/manage-billing.asciidoc b/serverless/pages/manage-billing.asciidoc index 101903e..1d70c61 100644 --- a/serverless/pages/manage-billing.asciidoc +++ b/serverless/pages/manage-billing.asciidoc @@ -8,14 +8,6 @@ Manage billing ++++ -preview:[] - -.Serverless billing starts June 1, 2024 -[IMPORTANT] -==== -Until May 31, 2024, your serverless consumption will not incur any charges, but will be visible along with your total Elastic Cloud consumption on the https://cloud.elastic.co/billing/usage[Billing Usage page]. Unless you are in a trial period, usage on or after June 1, 2024 will be deducted from your existing Elastic Cloud credits or be billed to your active payment method. -==== - You can manage the billing details of your organization directly from the Elastic Cloud console. . Navigate to https://cloud.elastic.co/[cloud.elastic.co] and log in to your Elastic Cloud account. diff --git a/serverless/pages/manage-org.asciidoc b/serverless/pages/manage-org.asciidoc index a74ca77..a65f809 100644 --- a/serverless/pages/manage-org.asciidoc +++ b/serverless/pages/manage-org.asciidoc @@ -4,8 +4,6 @@ // :description: Manage your instances, users, and settings. // :keywords: serverless, general, organization, overview -preview:[] - When you sign up to Elastic Cloud, you create an **organization**. This organization is the umbrella for all of your Elastic Cloud resources, users, and account settings. Every organization has a unique identifier. Bills are invoiced according to the billing contact and details that you set for your organization. diff --git a/serverless/pages/manage-your-project-rest-api.asciidoc b/serverless/pages/manage-your-project-rest-api.asciidoc index 6b8ce3f..bc6e999 100644 --- a/serverless/pages/manage-your-project-rest-api.asciidoc +++ b/serverless/pages/manage-your-project-rest-api.asciidoc @@ -4,8 +4,6 @@ // :description: Manage your organization's serverless projects using the REST API. // :keywords: serverless, project, manage, rest, api -preview:[] - You can manage serverless projects using the https://www.elastic.co/docs/api/doc/elastic-cloud-serverless[Elastic Cloud Serverless REST API]. This API allows you to create, update, and delete projects, as well as manage project features and usage. [TIP] diff --git a/serverless/pages/manage-your-project.asciidoc b/serverless/pages/manage-your-project.asciidoc index b9fc3b5..ffa9a0d 100644 --- a/serverless/pages/manage-your-project.asciidoc +++ b/serverless/pages/manage-your-project.asciidoc @@ -4,8 +4,6 @@ // :description: Configure project-wide features and usage. // :keywords: serverless, elasticsearch, project, manage -preview:[] - To manage a project: . Navigate to https://cloud.elastic.co/[cloud.elastic.co]. @@ -34,17 +32,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/maps.asciidoc b/serverless/pages/maps.asciidoc index d289dfd..17655ac 100644 --- a/serverless/pages/maps.asciidoc +++ b/serverless/pages/maps.asciidoc @@ -4,8 +4,6 @@ // :description: Create maps from your geographical data. // :keywords: serverless, Security -preview:[] - This content applies to: {sec-badge} In **{project-settings} → {maps-app}** you can: diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc index 51f0ed8..4e4df2b 100644 --- a/serverless/pages/pricing.asciidoc +++ b/serverless/pages/pricing.asciidoc @@ -4,53 +4,48 @@ // :description: Learn about how Elasticsearch usage affects pricing. // :keywords: serverless, elasticsearch, overview -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 fraction of RAM, CPU, and local disk for caching. -{es} 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 {es} 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 -metered and billed. +The number of VCUs you need is determined by: -include::../partials/minimum-vcus-detail.asciidoc[] +* 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]] -== Information about the VCU types (Search, Ingest, and ML) +== VCU types: Search, Indexing, and ML -There are three VCU types in {es}: +Elasticsearch uses three VCU types: -* **Indexing** — The VCUs used to index the incoming documents to be -stored in {es}. -* **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) +== Data storage and billing -For {es}, 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 -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]] == Managing {es} costs -You can control costs in a number of ways. Firstly there is the amount of -data that is retained. {es} 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 {es-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 {es-serverless} project rates, check the -https://www.elastic.co/pricing/serverless-search[{es-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 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]. diff --git a/serverless/pages/profile-queries-and-aggregations.asciidoc b/serverless/pages/profile-queries-and-aggregations.asciidoc index 67f67f0..e1c2b98 100644 --- a/serverless/pages/profile-queries-and-aggregations.asciidoc +++ b/serverless/pages/profile-queries-and-aggregations.asciidoc @@ -4,8 +4,6 @@ // :description: Diagnose and debug poorly performing search queries. // :keywords: serverless, dev tools, how-to -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} //// diff --git a/serverless/pages/project-and-management-settings.asciidoc b/serverless/pages/project-and-management-settings.asciidoc index a23249c..4cf44b6 100644 --- a/serverless/pages/project-and-management-settings.asciidoc +++ b/serverless/pages/project-and-management-settings.asciidoc @@ -1,8 +1,6 @@ // :description: Learn about capabilities available in multiple serverless solutions. // :keywords: serverless, observability, security, elasticsearch, overview -preview:[] - The documentation in this section describes shared capabilities that are available in multiple solutions. Look for the doc badge on each page to see if the page is valid for your solution: diff --git a/serverless/pages/project-settings.asciidoc b/serverless/pages/project-settings.asciidoc index c10545d..9dc0f0c 100644 --- a/serverless/pages/project-settings.asciidoc +++ b/serverless/pages/project-settings.asciidoc @@ -8,8 +8,6 @@ Management ++++ -preview:[] - Go to **Project settings**, then ** Management** to manage your indices, data views, saved objects, settings, and more. You can also open Management by using the {kibana-ref}/kibana-concepts-analysts.html#_finding_your_apps_and_objects[global search field]. diff --git a/serverless/pages/reports.asciidoc b/serverless/pages/reports.asciidoc index 533313c..4061479 100644 --- a/serverless/pages/reports.asciidoc +++ b/serverless/pages/reports.asciidoc @@ -4,8 +4,6 @@ // :description: View and manage generated reports. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} {kib} provides you with several options to share saved searches, dashboards, and visualizations. diff --git a/serverless/pages/rules.asciidoc b/serverless/pages/rules.asciidoc index b8cf47b..5c33895 100644 --- a/serverless/pages/rules.asciidoc +++ b/serverless/pages/rules.asciidoc @@ -4,8 +4,6 @@ // :description: Alerting works by running checks on a schedule to detect conditions defined by a rule. // :keywords: serverless, Elasticsearch, alerting, learn -preview:[] - This content applies to: {es-badge} In general, a rule consists of three parts: diff --git a/serverless/pages/run-api-requests-in-the-console.asciidoc b/serverless/pages/run-api-requests-in-the-console.asciidoc index fd540cc..b49d4f2 100644 --- a/serverless/pages/run-api-requests-in-the-console.asciidoc +++ b/serverless/pages/run-api-requests-in-the-console.asciidoc @@ -4,8 +4,6 @@ // :description: Use the Console to interact with Elastic REST APIs. // :keywords: serverless, dev tools, how-to -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} **Console** lets you interact with https://www.elastic.co/docs/api[{es} and Kibana serverless APIs] from your project. diff --git a/serverless/pages/saved-objects.asciidoc b/serverless/pages/saved-objects.asciidoc index bb8a4d7..dc0bd8e 100644 --- a/serverless/pages/saved-objects.asciidoc +++ b/serverless/pages/saved-objects.asciidoc @@ -4,8 +4,6 @@ // :description: Manage your saved objects, including dashboards, visualizations, maps, {data-sources}, and more. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} To get started, go to **{project-settings} → {manage-app} → {saved-objects-app}**: diff --git a/serverless/pages/search-playground.asciidoc b/serverless/pages/search-playground.asciidoc index 992ed6f..83aefb7 100644 --- a/serverless/pages/search-playground.asciidoc +++ b/serverless/pages/search-playground.asciidoc @@ -4,8 +4,6 @@ // :description: Test and edit Elasticsearch queries and chat with your data using LLMs. // :keywords: serverless, elasticsearch, search, playground, GenAI, LLMs -preview:[] - Use the Search Playground to test and edit {es} queries visually in the UI. Then use the Chat Playground to combine your {es} data with large language models (LLMs) for retrieval augmented generation (RAG). You can also view the underlying Python code that powers the chat interface, and use it in your own application. diff --git a/serverless/pages/search-with-synonyms.asciidoc b/serverless/pages/search-with-synonyms.asciidoc index c38ea8e..e107513 100644 --- a/serverless/pages/search-with-synonyms.asciidoc +++ b/serverless/pages/search-with-synonyms.asciidoc @@ -4,8 +4,6 @@ // :description: Use synonyms to search for words or phrases that have the same or similar meaning. // :keywords: serverless, elasticsearch, search, synonyms -preview:[] - Synonyms are words or phrases that have the same or similar meaning. They are an important aspect of search, as they can improve the search experience and increase the scope of search results. diff --git a/serverless/pages/search-your-data-semantic-search.asciidoc b/serverless/pages/search-your-data-semantic-search.asciidoc index 32b65fe..de30fe8 100644 --- a/serverless/pages/search-your-data-semantic-search.asciidoc +++ b/serverless/pages/search-your-data-semantic-search.asciidoc @@ -4,9 +4,9 @@ // :description: Find data based on the intent and contextual meaning of a search query with semantic search // :keywords: elasticsearch, elser, semantic search -preview:[] - -Semantic search is a search method that helps you find data based on the intent and contextual meaning of a search query, instead of a match on query terms (lexical search). +Semantic search is a search method that helps you find data based on the intent +and contextual meaning of a search query, instead of a match on query terms +(lexical search). Elasticsearch provides various semantic search capabilities using natural language processing (NLP) and vector search. Using an NLP model enables you to extract text embeddings out of text. Embeddings are vectors that provide a numeric representation of a text. Pieces of content with similar meaning have similar representations. diff --git a/serverless/pages/search-your-data-the-search-api.asciidoc b/serverless/pages/search-your-data-the-search-api.asciidoc index 1574332..dcf65a9 100644 --- a/serverless/pages/search-your-data-the-search-api.asciidoc +++ b/serverless/pages/search-your-data-the-search-api.asciidoc @@ -4,8 +4,6 @@ // :description: Run queries and aggregations with the search API. // :keywords: serverless, elasticsearch, API -preview:[] - A _search_ consists of one or more queries that are combined and sent to {es}. Documents that match a search's queries are returned in the _hits_, or _search results_, of the response. diff --git a/serverless/pages/search-your-data.asciidoc b/serverless/pages/search-your-data.asciidoc index b74c844..196e5b1 100644 --- a/serverless/pages/search-your-data.asciidoc +++ b/serverless/pages/search-your-data.asciidoc @@ -4,8 +4,6 @@ // :description: Use the search API to run queries on your data. // :keywords: serverless, elasticsearch, search -preview:[] - A search query, or query, is a request for information about data in {es} data streams or indices. You can think of a query as a question, written in a way {es} understands. Depending on your data, you can use a query to get answers to questions like: diff --git a/serverless/pages/serverless-differences.asciidoc b/serverless/pages/serverless-differences.asciidoc index 6ee6b81..7e3f19f 100644 --- a/serverless/pages/serverless-differences.asciidoc +++ b/serverless/pages/serverless-differences.asciidoc @@ -1,19 +1,111 @@ [[elasticsearch-differences]] = Differences from other {es} offerings +++++ +Serverless differences +++++ // :description: Understand how {es-serverless} differs from Elastic Cloud Hosted and self-managed offerings. // :keywords: serverless, elasticsearch -++++ -Serverless differences -++++ +<> handles all the infrastructure management for you, providing a fully managed {es} service. + +If you've used {es} before, you'll notice some differences in how you work with the service on {serverless-full}, because a number of APIs and settings are not required for serverless projects. + +This guide helps you understand what's different, what's available, and how to work effectively when running {es} on {serverless-full}. + +[discrete] +[[elasticsearch-differences-serverless-infrastructure-management]] +== Fully managed infrastructure + +{es-serverless} manages all infrastructure automatically, including: + +* Cluster scaling and optimization +* Node management and allocation +* Shard distribution and replication +* Resource utilization and monitoring + +This fully managed approach means many traditional {es} infrastructure APIs and settings are not available to end users, as detailed in the following sections. + +[discrete] +[[elasticsearch-differences-serverless-apis-availability]] +== API availability + +Because {es-serverless} manages infrastructure automatically, certain APIs are not available, while others remain fully accessible. + +[TIP] +==== +Refer to the https://www.elastic.co/docs/api/doc/elasticsearch-serverless[{es-serverless} API reference] for a complete list of available APIs. +==== + +The following categories of operations are unavailable: + +Infrastructure operations:: +* All `_nodes/*` operations +* All `_cluster/*` operations +* Most `_cat/*` operations, except for index-related operations such as `/_cat/indices` and `/_cat/aliases` + +Storage and backup:: +* All `_snapshot/*` operations +* Repository management operations -preview:[] +Index management:: +* `indices/close` operations +* `indices/open` operations +* Recovery and stats operations +* Force merge operations + +When attempting to use an unavailable API, you'll receive a clear error message: + +[source,json] +---- +{ + "error": { + "root_cause": [ + { + "type": "api_not_available_exception", + "reason": "Request for uri [/] with method [] exists but is not available when running in serverless mode" + } + ], + "status": 410 + } +} +---- + +[discrete] +[[elasticsearch-differences-serverless-settings-availability]] +== Settings availability + +In {es-serverless}, you can only configure {ref}/index-modules.html#index-modules-settings[index-level settings]. +Cluster-level settings and node-level settings are not required by end users and the `elasticsearch.yml` file is fully managed by Elastic. + +Available settings:: +*Index-level settings*: Settings that control how {es} documents are processed, stored, and searched are available to end users. These include: +* Analysis configuration +* Mapping parameters +* Search/query settings +* Indexing settings such as `refresh_interval` + +Managed settings:: +*Infrastructure-related settings*: Settings that affect cluster resources or data distribution are not available to end users. These include: +* Node configurations +* Cluster topology +* Shard allocation +* Resource management + +[discrete] +[[elasticsearch-differences-serverless-feature-categories]] +== Feature availability Some features that are available in Elastic Cloud Hosted and self-managed offerings are not available in {es-serverless}. -These features have either been replaced by a new feature, or are not applicable in the new Serverless architecture: +These features have either been replaced by a new feature, are planned to be released in future, or are not applicable in the new serverless architecture. + +[discrete] +[[elasticsearch-differences-serverless-features-replaced]] +=== Replaced features -* **Index lifecycle management ({ilm-init})** is not available, in favor of <>. +These features have been replaced by a new feature and are therefore not available on {es-serverless}: + +* *Index lifecycle management ({ilm-init})* is not available, in favor of <>. + In an Elastic Cloud Hosted or self-managed environment, {ilm-init} lets you automatically transition indices through data tiers according to your performance needs and retention requirements. This allows you to balance hardware costs with performance. {es-serverless} eliminates this @@ -22,21 +114,44 @@ complexity by optimizing your cluster performance for you. Data stream lifecycle is an optimized lifecycle tool that lets you focus on the most common lifecycle management needs, without unnecessary hardware-centric concepts like data tiers. + -* **Watcher** is not available, in favor of Kibana Alerts**. +* *Watcher* is not available, in favor of <>. + Kibana Alerts allows rich integrations across use cases like APM, metrics, security, and uptime. Prepackaged rule types simplify setup and hide the details of complex, domain-specific detections, while providing a consistent interface across Kibana. + +[discrete] +[[elasticsearch-differences-serverless-feature-planned]] +=== Planned features + +The following features are planned for future support in all {serverless-full} projects: + +* Reindexing from remote clusters +* Cross-project search and replication +* Snapshot and restore +* Migrations from non-serverless deployments +* Audit logging +* Authentication realms (native/SAML/OIDC/Kerberos/JWT) +* Clone index API +* Traffic filtering and VPCs + +The following {es-serverless} project-specific features are planned for future support: + +* {ref}/behavioral-analytics-overview.html[Behavioral Analytics] +* {ref}/search-application-overview.html[Search Applications] +* {enterprise-search-ref}/crawler.html[Managed web crawler] ++ +You can use the https://github.com/elastic/crawler[self-managed web crawler] in the meantime. + -* Certain APIs, API parameters, index, cluster and node level settings are not available. Refer to our -<> for a list of available APIs. -+ -{es-serverless} manages the underlying Elastic cluster for you, optimizing nodes, shards, and replicas for your use case. -Because of this, various management and monitoring APIs, API parameters and settings are not available on Serverless. -+ -* {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Scripted metric aggregations] are not available. +* {ref}/es-native-connectors.html[Elastic managed Search connectors] ++ +You can use {ref}/es-build-connector.html[self-managed Search connectors] in the meantime. -.Other limitations -[IMPORTANT] -==== -For serverless technical preview limitations, refer to <>. -==== +[discrete] +[[elasticsearch-differences-serverless-feature-unavailable]] +=== Unplanned features + +The following features are not available in {es-serverless} and are not planned for future support: + +* https://www.elastic.co/guide/en/cloud/current/ec-custom-bundles.html[Custom plugins and bundles] +* https://www.elastic.co/guide/en/elasticsearch/hadoop/current/reference.html[{es} for Apache Hadoop] +* {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Scripted metric aggregations] \ No newline at end of file diff --git a/serverless/pages/tags.asciidoc b/serverless/pages/tags.asciidoc index 88e1615..5c126c6 100644 --- a/serverless/pages/tags.asciidoc +++ b/serverless/pages/tags.asciidoc @@ -4,8 +4,6 @@ // :description: Use tags to categorize your saved objects, then filter for related objects based on shared tags. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} To get started, go to **{project-settings} → {manage-app} → {tags-app}**: diff --git a/serverless/pages/technical-preview-limitations.asciidoc b/serverless/pages/technical-preview-limitations.asciidoc index a307e05..830ff88 100644 --- a/serverless/pages/technical-preview-limitations.asciidoc +++ b/serverless/pages/technical-preview-limitations.asciidoc @@ -1,25 +1,10 @@ [[elasticsearch-technical-preview-limitations]] -= Technical preview limitations += Limitations // :description: Review the limitations that apply to {es-serverless} projects. // :keywords: serverless, elasticsearch -preview:[] -The following are currently not available: +// This page is not included in the index file, so it is not visible in the navigation menu anymore. HTTP redirects will be set up. -* Custom plugins and custom bundles -* Reindexing from remote clusters -* Cross-cluster search and cross-cluster replication -* Snapshot and restore -* Clone index API -* Migrations from non-serverless {es} deployments. In the interim, you can <> to move data to and from serverless projects. -* Custom roles -* Audit logging -* {es} for Apache Hadoop - -Currently, workloads outside of the following ranges may experience higher latencies (greater than sub-second): - -* Search queries on indices greater than 150GB -* Index queries per second (QPS) greater than 1000 -* Search queries per second (QPS) greater than 1800 +Refer to <> for a comparison of {es-serverless} with other Elastic Cloud offerings. \ No newline at end of file diff --git a/serverless/pages/transforms.asciidoc b/serverless/pages/transforms.asciidoc index 29e6187..c561356 100644 --- a/serverless/pages/transforms.asciidoc +++ b/serverless/pages/transforms.asciidoc @@ -4,8 +4,6 @@ // :description: Use transforms to pivot existing indices into summarized or entity-centric indices. // :keywords: serverless, Elasticsearch, Observability, Security -preview:[] - This content applies to: {es-badge} {obs-badge} {sec-badge} {transforms-cap} enable you to convert existing {es} indices into summarized diff --git a/serverless/pages/user-profile.asciidoc b/serverless/pages/user-profile.asciidoc index 5d7a04f..fb8d8b3 100644 --- a/serverless/pages/user-profile.asciidoc +++ b/serverless/pages/user-profile.asciidoc @@ -4,8 +4,6 @@ // :description: Manage your profile settings. // :keywords: serverless, general, profile, update -preview:[] - To edit your user profile, go to the user icon on the header bar and select **Profile**. [discrete] diff --git a/serverless/pages/welcome-to-serverless.asciidoc b/serverless/pages/welcome-to-serverless.asciidoc index a42f442..2d1f993 100644 --- a/serverless/pages/welcome-to-serverless.asciidoc +++ b/serverless/pages/welcome-to-serverless.asciidoc @@ -10,8 +10,6 @@ ++++ -preview:[] - Elastic serverless products allow you to deploy and use Elastic for your use cases without managing the underlying Elastic cluster, such as nodes, data tiers, and scaling. Serverless instances are fully-managed, autoscaled, and automatically upgraded by Elastic so you can focus more on gaining value and insight from your data. diff --git a/serverless/pages/what-is-elasticsearch-serverless.asciidoc b/serverless/pages/what-is-elasticsearch-serverless.asciidoc index 58fbb60..ba15f26 100644 --- a/serverless/pages/what-is-elasticsearch-serverless.asciidoc +++ b/serverless/pages/what-is-elasticsearch-serverless.asciidoc @@ -4,14 +4,14 @@ // :description: Build search solutions and applications with {es-serverless}. // :keywords: serverless, elasticsearch, overview -preview:[] +Elasticsearch allows you to build custom applications. Whether you have structured or unstructured text, numerical data, or geospatial data, Elasticsearch can efficiently store and index it in a way that supports fast searches. -[TIP] +.Understanding Elasticsearch on serverless +[IMPORTANT] ==== If you haven't used {es} before, first learn the basics in the https://www.elastic.co/guide/en/elasticsearch/reference/current/elasticsearch-intro.html[core {es} documentation]. ==== - {es} is one of the three available project types on <>. This project type enables you to use the core functionality of {es}: searching, indexing, storing, and analyzing data of all shapes and sizes. @@ -31,12 +31,9 @@ a| [.card-title]#<># + Get started by creating your first {es} project on serverless. | 🔌 -a| [.card-title]#<># + +a| [.card-title]#<># + Learn how to connect your applications to your {es-serverless} endpoint. -// TODO add coming link to new page about connecting to your serverless endpoint -// <> - | ⤵️ a| [.card-title]#<># + Learn how to get your data into {es} and start building your search application. diff --git a/serverless/pages/what-is-serverless.asciidoc b/serverless/pages/what-is-serverless.asciidoc index 8999cbd..f3ca114 100644 --- a/serverless/pages/what-is-serverless.asciidoc +++ b/serverless/pages/what-is-serverless.asciidoc @@ -3,8 +3,8 @@ // :keywords: serverless -Serverless projects use the core components of the {stack}, such as {es} and {kib}, and are based on https://www.elastic.co/blog/elastic-serverless-architecture[an architecture that -decouples compute and storage]. Search and indexing operations are separated, which offers high flexibility for scaling your workloads while ensuring +Serverless projects use the core components of the {stack}, such as {es} and {kib}, and are based on an architecture that +decouples compute and storage. Search and indexing operations are separated, which offers high flexibility for scaling your workloads while ensuring a high level of performance. **Management free.** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, @@ -21,12 +21,6 @@ The size of the cache layer and the volume of data it holds depend on <