Merge remote-tracking branch 'origin/main' into remote_clusters_snippets2

Author: eedugon

deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md

@@ -16,7 +16,7 @@ Subscribe to {{ecloud}} directly from the Google Cloud Platform (GCP). You then
 
 Some differences exist when you subscribe to {{ecloud}} through the GCP Marketplace:
 
-* New customers {{ecloud}} obtain a 7-day trial period. During this period, you can use a single deployment and three projects of {{ecloud}}. After this period, usage-based billing starts, unless you delete your cloud resources. Note that once customers unsubscribe from the GCP offer, their trial will end immediately. Even if they resubscribe, they will not be able to resume the trial.
+* New {{ecloud}} customers obtain a 7-day trial period. During this period, you can use a single deployment and three projects of {{ecloud}}. After this period, usage-based billing starts, unless you delete your cloud resources. Note that once customers unsubscribe from the GCP offer, their trial will end immediately. Even if they resubscribe, they will not be able to resume the trial.
 * Pricing for an {{ecloud}} subscription through the GCP Marketplace follows the pricing outlined on the [{{ecloud}}](https://console.cloud.google.com/marketplace/product/endpoints/elasticsearch-service.gcpmarketplace.elastic.co) page in the GCP Marketplace. Pricing is based the {{ecloud}} [billing dimensions](../../cloud-organization/billing.md#pricing-model).
 * To access your billing information at any time go to **Account & Billing**. You can also go to **Account & Billing** and then **Usage** to view your usage hours and units per hour.
 

deploy-manage/monitor/_snippets/autoops-cc-regions.md

@@ -1,7 +1,7 @@
 | Region | Name |
 | --- | --- | 
-| us-east-2 | Ohio |
-| eu-west-1 | Ireland |
-| ap-northeast-1 | Tokyo |
+| us-east-2 | US East (Ohio) |
+| eu-west-1 | EU (Ireland) |
+| ap-northeast-1 | Asia Pacific (Tokyo) |
 
-More regions are coming soon.
+More regions are coming soon.

explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md

@@ -21,7 +21,7 @@ When you’re done, you’ll have a complete overview of the sample web logs dat
 
 ## Add the data and create the dashboard [add-the-data-and-create-the-dashboard-advanced]
 
-Add the sample eCommerce data, and create and set up the dashboard.
+Add the sample eCommerce data, and set up the dashboard.
 
 1. [Install the eCommerce sample data set](../index.md#gs-get-data-into-kibana).
 2. Go to **Dashboards**.

explore-analyze/elastic-inference/eis.md

@@ -53,7 +53,9 @@ This is particularly relevant when using the [_bulk API](https://www.elastic.co/
 
 ## Pricing 
 
-All models on EIS incur a charge per million tokens. The pricing details are at our [Pricing page](https://www.elastic.co/pricing/serverless-search) for the Elastic Managed LLM and ELSER. 
+All models on EIS incur a charge per million tokens. The pricing details are at our [Pricing page](https://www.elastic.co/pricing/serverless-search) for the Elastic Managed LLM and ELSER.
+
+Note that this pricing models differs from the existing [Machine Learning Nodes](https://www.elastic.co/docs/explore-analyze/machine-learning/data-frame-analytics/ml-trained-models), which is billed via VCUs consumed.
 
 ## Rate Limits
 

reference/fleet/elastic-agent-standalone-logging-config.md

@@ -29,7 +29,7 @@ agent.logging.files:
 
 You can specify the following settings in the Logging section of the `elastic-agent.yml` config file.
 
-Some outputs will log raw events on errors like indexing errors in the Elasticsearch output, to prevent logging raw events (that may contain sensitive information) together with other log messages, a different log file, only for log entries containing raw events, is used. It will use the same level, selectors and all other configurations from the default logger, but it will have it’s own file configuration.
+Some outputs will log raw events on errors like indexing errors in the Elasticsearch output, to prevent logging raw events (that may contain sensitive information) together with other log messages, a different log file, only for log entries containing raw events, is used. It will use the same level, selectors and all other configurations from the default logger, but it will have its own file configuration.
 
 Having a different log file for raw events also prevents event data from drowning out the regular log files. Use `agent.logging.event_data` to configure the events logger.
 

release-notes/elastic-observability/known-issues.md

@@ -156,5 +156,38 @@ After upgrading a cluster, Collector and Symbolizer endpoints may not be configu
     DELETE kbn:/api/fleet/package_policies/<elastic-universal-profiling-symbolizer-id>?force=true
     ```
 
+::::
+
+:::{dropdown} Error when using the Opentelemetry onboarding flow using EDOT Collector
+Applies to: {{stack}} 9.1.6, 9.2.0
+
+**Details**
+
+Users trying to collect logs and host metrics using the Elastic distribution of the OTel collector will see error when using the OpenTelemetry quickstart onboarding flow:
+
+```
+> sudo ./otelcol --config otel.yml
+
+Starting in otel mode
+failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
+
+'exporters' error reading configuration for "otlp/ingest": decoding failed due to the following error(s):
+
+'sending_queue' decoding failed due to the following error(s):
+
+'batch' decoding failed due to the following error(s):
+
+'' has invalid keys: flush_interval
+
+```
+
+**Workaround**
+
+To work around this issue, manually update the configuration of the generated `otel.yaml` file to replace incorrect key `flush_interval` with the correct key `flush_timeout`.
+
+```yaml
+batch:
+  flush_timeout: 1s
+```
 
 ::::

solutions/search/agent-builder/get-started.md

@@ -26,24 +26,19 @@ You can set up a new [space](/deploy-manage/manage-spaces.md) to use the solutio
 
 :::::{step} Enable {{agent-builder}}
 
-
-<!-- 
-
-TODO: uncomment once default enabled is live on serverless
-
 ::::{applies-switch}
 
 :::{applies-item} { "serverless": "preview", "elasticsearch" }
 
 {{agent-builder}} is enabled by default in serverless {{es}} projects.
 
-Find **Agents** in the navigation menu to begin using the feature, or search for **Agents** in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 
+Find **Agents** in the navigation menu to begin using the feature, or search for **Agents** in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
 :::
 
 :::{applies-item} stack: preview 9.2
--->
-You have to enable {{agent-builder}} to get started.
+
+You have to enable {{agent-builder}} to get started on non-serverless deployments.
 
 You can enable the features using the UI:
 

solutions/search/agent-builder/models.md

@@ -10,10 +10,6 @@ applies_to:
 
 # Using different models in {{agent-builder}}
 
-:::{important}
-Due to phased rollout, the ability to use different models may not be immediately available in your project.
-:::
-
 {{agent-builder}} uses large language models (LLMs) to power agent reasoning and decision-making. By default, agents use the Elastic Managed LLM, but you can configure other models through Kibana connectors.
 
 ## Default model configuration

solutions/security/ai/ai-assistant.md

@@ -125,7 +125,7 @@ System Prompts and Quick Prompts can also be [configured](#configure-ai-assistan
 Be sure to specify which language you’d like AI Assistant to use when writing a query. For example: "Can you generate an Event Query Language query to find four failed logins followed by a successful login?"
 
 ::::{tip}
-AI Assistant can remember particular information you tell it to remember. For example, you could tell it: "When anwering any question about srv-win-s1-rsa or an alert that references it, mention that this host is in the New York data center". This will cause it to remember the detail you highlighted.
+AI Assistant can remember particular information you tell it to remember. For example, you could tell it: "When answering any question about srv-win-s1-rsa or an alert that references it, mention that this host is in the New York data center". This will cause it to remember the detail you highlighted.
 ::::
 
 ## Share conversations

solutions/security/detect-and-alert/prebuilt-rules-update-modified-unmodified.md

@@ -82,7 +82,7 @@ This table describes statuses that might appear for rule fields being updated.
 | **Ready for update** | Displays when there are no conflicts to resolve.<br><br>Further action is not required for the field. It is ready to be updated.<br> |
 | **No update** | Displays when the field is not being updated by Elastic, but the current field value differs from the original one. This typically happens when the field's value was changed after the prebuilt rule was initially installed.<br><br>Further action is not required for the field. It is ready to be updated.<br><br> **Tip**: You can still change the final field update, if needed. To do so, make your changes in the **Final update** section and save them.<br><br> |
 | **Review required** | Displays when Elastic auto-resolves a conflict between the current field value and the value from the incoming Elastic update.<br><br>You must accept or edit the field's final update and save the changes. Refer to [Resolve and reduce update conflicts](/solutions/security/detect-and-alert/prebuilt-rules-update-modified-unmodified.md#resolve-reduce-rule-conflicts) to learn more about auto-resolved conflicts and how to reduce future conflicts.<br> |
-| **Action required** | Displays when Elastic could not auto-resolve the conflict between the current field value and the value from the incoming Elastic update.<br><br>You must manually set and save the field's final update. Refer to Refer to [Resolve and reduce update conflicts](/solutions/security/detect-and-alert/prebuilt-rules-update-modified-unmodified.md#resolve-reduce-rule-conflicts) to learn more about conflicts that need manual fixes and how to reduce future conflicts.<br> |
+| **Action required** | Displays when Elastic could not auto-resolve the conflict between the current field value and the value from the incoming Elastic update.<br><br>You must manually set and save the field's final update. Refer to [Resolve and reduce update conflicts](/solutions/security/detect-and-alert/prebuilt-rules-update-modified-unmodified.md#resolve-reduce-rule-conflicts) to learn more about conflicts that need manual fixes and how to reduce future conflicts.<br> |
 
 
 ## Resolve and reduce update conflicts [resolve-reduce-rule-conflicts]
@@ -107,4 +107,4 @@ If Elastic can't resolve a conflict, you must manually fix it before updating th
 
 3. Click **Save and accept** to apply your changes. The field's status changes to `Ready for update`. 
 
-After you've resolved the remaining conflicts, click **Update rule** to accept the changes and install the updated version.
+After you've resolved the remaining conflicts, click **Update rule** to accept the changes and install the updated version.