Merge branch 'main' into remote_clusters_self_ssl

Author: eedugon

deploy-manage/cloud-organization/billing/manage-subscription.md

@@ -72,6 +72,9 @@ You can [change your subscription level](/deploy-manage/cloud-organization/billi
 `Field-level or document-level security`
 :   Remove any user role configurations based on field or document access [through the API](/deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md) or the {{kib}} [Roles](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md) page.
 
+`ES|QL cross-cluster search`
+:   Discontinue all [ES|QL CCS queries](elasticsearch://reference/query-languages/esql/esql-cross-clusters.md) or upgrade license tier to Enterprise.
+
 ::::{note}
 After you have made your changes to the deployment, it can take up to one hour to clear the notification banner.
 ::::

deploy-manage/deploy/cloud-on-k8s/elastic-stack-configuration-policies.md

@@ -11,14 +11,17 @@ products:
 # {{stack}} configuration policies [k8s-stack-config-policy]
 
 ::::{warning}
-We have identified an issue with {{es}} 8.15.1 and 8.15.2 that prevents security role mappings configured via Stack configuration policies to work correctly. Avoid these versions and upgrade to 8.16.0 to remedy this issue if you are affected.
+We have identified an issue with {{es}} 8.15.1 and 8.15.2 that prevents security role mappings configured via Stack configuration policies to work correctly. Avoid these versions and upgrade to 8.16+ to remedy this issue if you are affected.
 ::::
 
 
 ::::{note}
 This requires a valid Enterprise license or Enterprise trial license. Check [the license documentation](../../license/manage-your-license-in-eck.md) for more details about managing licenses.
 ::::
 
+::::{note}
+Component templates created in configuration policies cannot currently be referenced from index templates created through the {{es}} API or {{kib}} UI.
+::::
 
 Starting from ECK `2.6.1` and {{es}} `8.6.1`, {{stack}} configuration policies allow you to configure the following settings for {{es}}:
 

deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md

@@ -6,13 +6,13 @@ products:
   - id: cloud-kubernetes
 ---
 
-# Propagate Labels and Annotations [k8s-propagate-labels-annotations]
+# Propagate labels and annotations [k8s-propagate-labels-annotations]
 
 Starting with version `3.1.0`, {{eck}} supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}.
 
 The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by {{eck}}.
 
-```yaml
+```yaml subs=true
 apiVersion: elasticsearch.k8s.elastic.co/v1
 kind: Elasticsearch
 metadata:
@@ -29,7 +29,7 @@ metadata:
     my-label2: "my-label2-value"
   name: elasticsearch-sample
 spec:
-  version: 9.1.0
+  version: {{version.stack}}
   nodeSets:
     - name: default
       config:
@@ -60,7 +60,7 @@ service/elasticsearch-sample-es-transport       ClusterIP   None             <no
 
 It is possible to use `*` as a wildcard to propagate all labels and annotations from the parent resource to the child resources. For example:
 
-```yaml
+```yaml subs=true
 apiVersion: elasticsearch.k8s.elastic.co/v1
 kind: Elasticsearch
 metadata:
@@ -70,7 +70,7 @@ metadata:
     eck.k8s.alpha.elastic.co/propagate-labels: "*"
   name: elasticsearch-sample
 spec:
-  version: 9.1.0
+  version: {{version.stack}}
   nodeSets:
     - name: default
       config:

deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md

@@ -80,8 +80,8 @@ If you already have an {{ecloud}} account:
 :sync: new
 
 If you don’t have an existing {{ecloud}} account: 
-1. Sign up for an account. 
-2. Follow the prompts on your screen to create an organization.
+1. Go to the [Cloud Connected Services sign up](https://cloud.elastic.co/registration?onboarding_service_type=ccm) page. 
+2. Follow the prompts on your screen to sign up for {{ecloud}} and create an organization.
 3. Go through the installation wizard as detailed in the following sections.
 ::::
 

explore-analyze/elastic-inference/eis.md

@@ -64,9 +64,9 @@ Performance may vary during the Technical Preview.
 Batches are limited to a maximum of 16 documents.
 This is particularly relevant when using the [_bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-bulk) for data ingestion.
 
-#### Rate Limits 
+#### Rate limits 
 
-Rate limit for search and ingest is currently at 500 requests per minute.
+Rate limit for search and ingest is currently at 500 requests per minute. This allows you to ingest approximately 8000 documents per minute at 16 documents per request.
 
 ## Pricing 
 

explore-analyze/images/elasticsearch-reference-esql-discover-query-history.png

@@ -83,18 +83,18 @@ FROM kibana_sample_data_logs | LIMIT 10
 
 ### Make your query readable [_make_your_query_readable]
 
-For readability, you can put each processing command on a new line. The following query is identical to the previous one:
+For readability, you can put each processing command on a new line and add indentation. The following query is identical to the previous one:
 
 ```esql
 FROM kibana_sample_data_logs
-| LIMIT 10
+  | LIMIT 10
 ```
 
-You can do that using the **Add line breaks on pipes** button from the query editor’s footer.
+You can do that automatically using the {icon}`pipeBreaks` **Prettify query** button from the query editor’s footer.
 
 :::{image} /explore-analyze/images/esql-line-breakdown.gif
-:alt: Automatic line breaks for ES|QL queries
-:width: 50%
+:alt: Automatic line breaks and indentation for ES|QL queries
+:width: 75%
 :::
 
 You can adjust the editor’s height by dragging its bottom border to your liking.
@@ -107,12 +107,21 @@ A query may result in warnings, for example when querying an unsupported field t
 
 ### Query history [esql-kibana-query-history]
 
-You can reuse your recent {{esql}} queries in the query bar. In the query bar, click **Show recent queries**.
+You can reuse your recent {{esql}} queries in the query bar. In the query bar, select **Show recent queries**.
 
-You can then scroll through your recent queries:
+You can then: 
+- scroll through your most recent queries
+- {applies_to}`stack: ga 9.2` search for specific queries of your history
 
-:::{image} /explore-analyze/images/elasticsearch-reference-esql-discover-query-history.png
+:::{image} /explore-analyze/images/esql-history.gif
 :alt: esql discover query history
+:width: 75%
+:::
+
+:::{note}
+The maximum number of queries in the history depends on the version you're using:
+- {applies_to}`serverless: ga` {applies_to}`stack: ga 9.2` The query history can keep up to 50 KB of queries, which represents about 200 large queries, or about 300 short queries.
+- {applies_to}`stack: ga 9.0` The query history keeps your 20 most recent queries.
 :::
 
 ### Query help

explore-analyze/images/esql-history.gif

@@ -39,16 +39,16 @@ You can then **Save** and add it to an existing or a new dashboard using the sav
 
     ![Previewing an ESQL visualization](https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt69dcceb4f1e12bc1/66c752d6aff77d384dc44209/edit-esql-visualization.gif "")
 
-    :::{tip}
+    :::{note}
     {applies_to}`stack: ga 9.1` {applies_to}`serverless: ga`
 
-    When you edit the query and run it again, the visualization configuration persists as long as it is compatible with the query changes.
+    When you edit the query and run it again, the visualization configuration persists as long as it is compatible with the query changes. Refer to [](#chart-config-persist) for more details.
     :::
 
 4. You can bind controls to your ES|QL visualizations in dashboards by creating [ES|QL controls](../dashboards/add-controls.md#add-esql-control).
 5. Select **Apply and close** to save the visualization to the dashboard.
 
-## Customize the appearance of your {{esql}} visualization
+### Customize the appearance of your {{esql}} visualization
 
 When editing an {{esql}} visualization, you can customize the appearance of the chart. To do that:
 
@@ -62,8 +62,20 @@ When editing an {{esql}} visualization, you can customize the appearance of the
 
 3. Return to the previous menu, then **Apply and close** the configuration to save your changes.
 
-## Create an alert from your {{esql}} visualization
+### Chart configuration persistence over {{esql}} query update [chart-config-persist]
+```{applies_to}
+stack: ga 9.1
+serverless: ga
+```
 
+When you edit the {{esql}} query and run it again, the visualization configuration persists as you defined it as long as it is compatible with the query changes.
+
+The chart configuration resets or follows automatic suggestions when:
+- {applies_to}`stack: ga 9.2` You manually select a different chart type incompatible with the one previously selected.
+- {applies_to}`stack: ga 9.2` You create a new chart and haven't edited the visualization's options yet.
+- The query changes significantly and no longer returns compatible columns.
+
+## Create an alert from your {{esql}} visualization
 ```{applies_to}
 stack: ga 9.1
 serverless: