5193 ls output 8.19

.backportrc.json

@@ -1,7 +1,7 @@
 {
   "repoOwner": "elastic",
   "repoName": "ingest-docs",
-  "targetBranchChoices": ["main", "8.15","8.14","8.13","8.12", "8.11", "8.10", "8.9", "8.8", "8.7", "8.6", "7.17"],
+  "targetBranchChoices": ["8.18","8.17","8.16","8.15","8.14","8.13","8.12", "8.11", "8.10", "8.9", "8.8", "8.7", "8.6", "7.17"],
   "autoMerge": true,
   "autoMergeMethod": "squash",
   "branchLabelMapping": {

.github/CODEOWNERS

@@ -1 +1 @@
-* @elastic/platform-docs
+* @elastic/ingest-docs

docs/en/ingest-management/agent-policies.asciidoc

@@ -96,7 +96,11 @@ The following table illustrates the {fleet} user actions available to different
 |{y}
 |{n}
 
-|<<change-policy-enable-agent-monitoring,Enable agent monitoring>>
+|<<change-policy-enable-agent-monitoring,Configure agent monitoring>>
+|{y}
+|{n}
+
+|<<agent-policy-automatic-agent-upgrade,Configure an automatic {agent} upgrade>>
 |{y}
 |{n}
 
@@ -116,10 +120,6 @@ The following table illustrates the {fleet} user actions available to different
 |{y}
 |{n}
 
-|<<agent-policy-http-monitoring>>
-|{y}
-|{n}
-
 |<<agent-policy-log-level>>
 |{y}
 |{n}
@@ -162,6 +162,9 @@ Also see <<create-a-policy-no-ui>>.
 == Add an integration to a policy
 
 An {agent} policy consists of one or more integrations that are applied to the agents enrolled in that policy.
+When you add an integration, the policy created for that integration can be shared with multiple {agent} policies.
+This reduces the number of integrations policies that you need to actively manage.
+
 To add a new integration to one or more {agent} policies:
 
 . In {fleet}, click **Agent policies**.
@@ -184,6 +187,11 @@ You can update the settings for an installed integration at any time:
 . In {kib}, go to the **Integrations** page.
 . On the **Integration policies** tab, for the integration that you like to update open the **Actions** menu and select **Edit integration**.
 . On the **Edit <integration>** page you can update any configuration settings and also update the list of {agent} polices to which the integration is added.
++
+If you clear the **Agent policies** field, the integration will be removed from any {agent} policies to which it had been added.
++
+To identify any integrations that have been "orphaned", that is, not associated with any {agent} policies, check the **Agent polices** column on the **Integration policies** tab.
+Any integrations that are installed but not associated with an {agent} policy are as labeled as `No agent policies`.
 
 [discrete]
 [[apply-a-policy]]
@@ -301,23 +309,76 @@ Note that adding custom tags is not supported for a small set of inputs:
 * `cloud-defend`
 * `fleet-server`
 * `pf-elastic-collector`, `pf-elastic-symbolizer`, and `pf-host-agent`
+* `endpoint` inputs. Instead, use the advanced settings (`*.advanced.document_enrichment.fields`) of the {elastic-defend} Integration.
 
 
 [discrete]
 [[change-policy-enable-agent-monitoring]]
-== Enable agent monitoring
+== Configure agent monitoring
 
-Use this setting to collect monitoring logs and metrics from {agent}. All monitoring data will be written to the specified **Default namespace**.
+Use these settings to collect monitoring logs and metrics from {agent}. All monitoring data will be written to the specified **Default namespace**.
 
 . In {fleet}, click **Agent policies**.
 Select the name of the policy you want to edit.
 
-. Click the **Settings** tab and scroll to **Enable agent monitorings**.
+. Click the **Settings** tab and scroll to **Agent monitoring**.
 
 . Select whether to collect agent logs, agent metrics, or both, from the {agents} that use the policy.
-
++
 When this setting is enabled an {agent} integration is created automatically.
 
+. Expand the **Advanced monitoring options** section to access <<advanced-agent-monitoring-settings,advanced settings>>.
+
+. Save your changes for the updated monitoring settings to take effect.
+
+[discrete]
+[[advanced-agent-monitoring-settings]]
+=== Advanced agent monitoring settings
+
+**HTTP monitoring endpoint**
+
+Enabling this setting exposes a `/liveness` API endpoint that you can use to monitor {agent} health according to the following HTTP codes:
+
+* `200`: {agent} is healthy. The endpoint returns a `200` OK status as long as {agent} is responsive and can process configuration changes.
+* `500`: A component or unit is in a failed state.
+* `503`: The agent coordinator is unresponsive.
+
+You can pass a `failon` parameter to the `/liveness` endpoint to determine what component state will result in a `500` status. For example, `curl 'localhost:6792/liveness?failon=degraded'` will return `500` if a component is in a degraded state.
+
+The possible values for `failon` are:
+
+* `degraded`: Return an error if a component is in a degraded state or failed state, or if the agent coordinator is unresponsive.
+* `failed`: Return an error if a unit is in a failed state, or if the agent coordinator is unresponsive.
+* `heartbeat`: Return an error only if the agent coordinator is unresponsive.
+
+If no `failon` parameter is provided, the default `failon` behavior is `heartbeat`.
+
+The HTTP monitoring endpoint can also be link:https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-liveness-http-request[used with Kubernetes], to restart the container for example.
+
+When you enable this setting, you need to provide the host URL and port where the endpoint can be accessed. Using the default `localhost` is recommended.
+
+When the HTTP monitoring endpoint is enabled you can also select to **Enable profiling at `/debug/pprof`**. This controls whether the {agent} exposes the `/debug/pprof/` endpoints together with the monitoring endpoints.
+
+The heap profiles available from `/debug/pprof/` are included in <<elastic-agent-diagnostics-command,{agent} diagnostics>> by default. CPU profiles are also included when the `--cpu-profile` option is included. For full details about the profiles exposed by `/debug/pprof/` refer to the link:https://pkg.go.dev/net/http/pprof[pprof package documentation].
+
+Profiling at `/debug/pprof` is disabled by default. Data produced by these endpoints can be useful for debugging but present a security risk. It's recommended to leave this option disabled if the monitoring endpoint is accessible over a network.
+
+**Diagnostics rate limiting**
+
+You can set a rate limit for the action handler for diagnostics requests coming from {fleet}. The setting affects only {fleet}-managed {agents}. By default, requests are limited to an interval of `1m` and a burst value of `1`. This setting does not affect diagnostics collected through the CLI.
+
+**Diagnostics file upload**
+
+This setting configures retries for the file upload client handling diagnostics requests coming from {fleet}. The setting affects only {fleet}-managed {agents}. By default, a maximum of `10` retries are allowed with an initial duration of `1s` and a backoff duration of `1m`. The client may retry failed requests with exponential backoff.
+
+[discrete]
+[[agent-policy-automatic-agent-upgrade]]
+== Configure an automatic {agent} upgrade
+
+For a high-scale deployment of {fleet}, you can configure an automatic, gradual rollout of a new minor or patch version to a percentage of the {agents} in your policy. For more information, refer to <<auto-upgrade-agents,Auto-upgrade agents enrolled in a policy>>.
+
+NOTE: This feature is only available for certain subscription levels. For more information, refer to {subscriptions}[{stack} subscriptions].
+
 [discrete]
 [[change-policy-output]]
 == Change the output of a policy
@@ -409,22 +470,6 @@ Select the name of the policy you want to edit.
 
 . Set **Limit CPU usage** as needed. For example, to limit Go processes supervised by {agent} to two operating system threads each, set this value to `2`.
 
-[discrete]
-[[agent-policy-http-monitoring]]
-== Override the default monitoring port
-
-You can override the default port that {agent} uses to send monitoring data. It's useful to be able to adjust this setting if you have an application running on the machine on which the agent is deployed, and that is using the same port.
-
-. In {fleet}, click **Agent policies**.
-Select the name of the policy you want to edit.
-
-. Click the **Settings** tab and scroll to **Advanced settings**.
-
-//. Set **Agent HTTP monitoring** setting to enabled, and then specify a host and port for the monitoring data output.
-. Specify a host and port for the monitoring data output.
-
-//. Enable **buffer.enabled** if you'd like {agent} and {beats} to collect metrics into an in-memory buffer and expose these through a `/buffer` endpoint. This data can be useful for debugging or if the {agent} has issues communicating with {es}. Enabling this option may slightly increase process memory usage.
-
 [discrete]
 [[agent-policy-log-level]]
 == Set the {agent} log level
@@ -524,4 +569,6 @@ The unenroll task runs every ten minutes, and it unenrolls a maximum of one thou
 [[agent-policy-scale]]
 == Policy scaling recommendations
 
-A single instance of {fleet} supports a maximum of 500 {agent} policies. If more policies are configured, UI performance might be impacted.
+A single instance of {fleet} supports a maximum of 1000 {agent} policies. If more policies are configured, UI performance might be impacted. The maximum number of policies is not affected by the number of spaces in which the policies are used.
+
+If you are using {agent} with link:{serverless-docs}[{serverless-full}], the maximum supported number of {agent} policies is 500.

docs/en/ingest-management/beats-agent-comparison.asciidoc

@@ -271,9 +271,9 @@ The following table shows a comparison of capabilities supported by {beats} and
 
 |Run without root on host
 |{y}
-|{n}
-|{n}
-|{fleet}-managed {agent}s require root permission, in particular for {elastic-defend}. Standalone {agent}s also require root permissions. {beats} requires root permission only if it's configured to capture data that requires that level of permission.
+|{y}
+|{y}
+|{fleet}-managed {agent}s, Standalone {agent}s, and {beats} require root permission only if they're configured to capture data that requires that level of permission.
 
 |Multiple outputs
 |{y}