Merge branch 'main' into 3284/convert-lookup

Author: kilfoyle

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

@@ -123,8 +123,8 @@ With this authentication method, you need to create an API key to grant access t
 
 1. From your {{ecloud}} home page, select a deployment.
 2. Go to **Stack management** > **API keys** and select **Create API key**.
-4. In the flyout, enter a name for your key and select **User API key**.
-5. Enable **Control security privileges** and enter the following script:
+3. In the flyout, enter a name for your key and select **User API key**.
+4. Enable **Control security privileges** and enter the following script:
 ```json
 {
  "autoops": {
@@ -287,8 +287,8 @@ You can use the same installation command to connect multiple clusters, but each
 
 Complete the following steps to disconnect your cluster from your Cloud organization. You need the **Organization owner** [role](/deploy-manage/monitor/autoops/cc-manage-users.md#assign-roles) to perform this action.
 
-2. Based on your [installation method](#select-installation-method), complete the steps to stop {{agent}} from shipping metrics to {{ecloud}}.
-1. Log in to [{{ecloud}}](https://cloud.elastic.co/home).
+1. Based on your [installation method](#select-installation-method), complete the steps to stop {{agent}} from shipping metrics to {{ecloud}}.
+2. Log in to [{{ecloud}}](https://cloud.elastic.co/home).
 3. On the **Connected clusters** page or the **Connected clusters** section of the home page, locate the cluster you want to disconnect.
 4. From that cluster’s actions menu, select **Disconnect cluster**.
 5. Enter the cluster’s name in the field that appears and then select **Disconnect cluster**.

explore-analyze/find-and-organize/data-views.md

@@ -37,6 +37,7 @@ In certain apps, you can also query your {{es}} data using [{{esql}}](elasticsea
   - `Data View Management` {{kib}} privilege.
   - `view_index_metadata` {{es}} privilege.
 * If a read-only indicator appears, you have insufficient privileges to create or save {{data-sources}}. In addition, the buttons to create {{data-sources}} or save existing {{data-sources}} are not visible.
+* {applies_to}`stack: ga 9.2` Some data views are exclusively configured and **managed** by Elastic. You can view and use these managed data views, but you can't edit them. If you'd like to use a modified version of a managed data view, you can [duplicate it](#duplicate-managed-data-view) and edit that new copy as needed.
 
 
 ## Create a data view [settings-create-pattern]
@@ -678,3 +679,24 @@ The **Color** field formatter enables you to specify colors with ranges of value
 When you select the **Color** formatter, click **Add Color**, then specify the **Range**, **Text color**, and **Background color**.
 
 
+## Duplicate managed data views [duplicate-managed-data-view]
+```{applies_to}
+stack: ga 9.2
+```
+
+Some data views are exclusively configured and **managed** by Elastic. You can view and use these managed data views, but you can't edit them. If you'd like to use a modified version of a managed data view, you can duplicate it and edit that new copy as needed. To do this:
+
+1. Open the {{kib}} application where you want to use the data view. For example, **Discover** or **Lens**.
+   :::{note}
+   The duplication operation isn't available from the **Data Views** management page.
+   :::
+
+2. In the data view selection menu, select the managed data view that you want to duplicate.
+
+3. Still in the data view selection menu, select **Manage this data view**. A flyout with more details about the data view opens, and indicates that you can't edit it directly.
+
+   ![Manage this data view option](../images/manage-this-data-view.png "Manage this data view option =50%")
+
+4. Select **Duplicate**. A Similar flyout opens where you can adjust the settings of the new copy of the managed data view.
+
+5. Finalize your edits, then select **Save data view to Kibana** or **Use without saving**, depending on your needs. By saving it to {{kib}}, you can retrieve it and use it again later.

explore-analyze/images/manage-this-data-view.png

@@ -89,7 +89,7 @@ As discussed above `@timestamp` is set to the timestamp from within the collecte
     lang: javascript
     source: >
       function process(event) {
-          event.put("event.created", Date.now());
+          event.Put("event.created", Date.now());
       }
 ```
 

manage-data/ingest/transform-enrich/ingest-lag.md

@@ -99,22 +99,6 @@ To add or edit an output:
 If the options for editing an output are grayed out, outputs are configured outside of {{fleet}}. For more information, refer to [{{fleet}} settings in {{kib}}](kibana://reference/configuration-reference/fleet-settings.md).
 ::::
 
-
-
-## Agent binary download settings [fleet-agent-binary-download-settings]
-
-{{agent}}s must be able to access the {{artifact-registry}} to download binaries during upgrades. By default {{agent}}s download artifacts from the artifact registry at `https://artifacts.elastic.co/downloads/`.
-
-For {{agent}}s that cannot access the internet, you can specify agent binary download settings, and then configure agents to download their artifacts from the alternate location. For more information about running {{agent}}s in a restricted environment, refer to [Air-gapped environments](/reference/fleet/air-gapped.md).
-
-To add or edit the source of binary downloads:
-
-1. Go to **{{fleet}} > Settings**.
-2. Under **Agent Binary Download**, select **Add agent binary source** or **Edit**.
-3. Set the agent binary source name.
-4. For **Host**, specify the address where you are hosting the artifacts repository.
-5. (Optional) To make this location the default, select **Make this host the default for all agent policies**. {{agent}}s use the default location if you don’t select a different agent binary source in the agent policy.
-
 ## Agent binary download settings [fleet-agent-binary-download-settings]
 
 {{agent}}s must be able to access the {{artifact-registry}} to download binaries during upgrades. By default {{agent}}s download artifacts from the artifact registry at `https://artifacts.elastic.co/downloads/`.

reference/fleet/fleet-settings.md

@@ -4,6 +4,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-configure-agent-config.html
 applies_to:
   stack: ga
+  serverless: unavailable
 products:
   - id: observability
   - id: apm