Merge branch 'main' into fix-logs-formatting

Author: mdbirnstiehl

reference/ingestion-tools/fleet/agent-command-reference.md

@@ -182,7 +182,6 @@ elastic-agent enroll --fleet-server-es <string>
                      [--force]
                      [--header <strings>]
                      [--help]
-                     [--non-interactive]
                      [--proxy-disabled]
                      [--proxy-header <strings>]
                      [--proxy-url <string>]
@@ -307,9 +306,6 @@ For more information about custom certificates, refer to [Configure SSL/TLS for
     We strongly recommend that you use a secure connection.
 
 
-`--non-interactive`
-:   Install {{agent}} in a non-interactive mode. This flag is helpful when using automation software or scripted deployments. If {{agent}} is already installed on the host, the installation will terminate.
-
 `--proxy-disabled`
 :   Disable proxy support including environment variables.
 

reference/ingestion-tools/fleet/logstash-output.md

@@ -25,6 +25,8 @@ outputs:
 
 To receive the events in {{ls}}, you also need to create a {{ls}} configuration pipeline. The {{ls}} configuration pipeline listens for incoming {{agent}} connections, processes received events, and then sends the events to {{es}}.
 
+Please be aware that the structure of the documents sent from {{agent}} to {{ls}} must not be modified by the pipeline. We recommend that the pipeline doesn’t edit or remove the fields and their contents. Editing the structure of the documents coming from {{agent}} can prevent the {{es}} ingest pipelines associated to the integrations in use to work correctly. We cannot guarantee that the {{es}} ingest pipelines associated to the integrations using {agent} can work with missing or modified fields.
+
 The following {{ls}} pipeline definition example configures a pipeline that listens on port `5044` for incoming {{agent}} connections and routes received events to {{es}}.
 
 ```yaml

solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md

@@ -26,8 +26,7 @@ To collect EC2 metrics, you typically need to install the Elastic [Amazon EC2 in
 
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
-:::::{dropdown} **Quick guide: Add data**
-::::{admonition}
+:::::{dropdown} Quick guide: Add data
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon EC2** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.

solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md

@@ -28,8 +28,7 @@ To collect Kinesis data stream metrics from Amazon CloudWatch, you typically nee
 
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
-:::::{dropdown} **Quick guide: Add data**
-::::{note}
+:::::{dropdown} Quick guide: Add data
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon Kinesis Data Stream** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.

solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md

@@ -24,8 +24,7 @@ To collect SQS metrics, you typically need to install the Elastic [Amazon SQS in
 
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
-:::::{dropdown} **Quick guide: Add data**
-::::{note}
+:::::{dropdown} Quick guide: Add data
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon SQS** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.

solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md

@@ -27,8 +27,7 @@ To collect S3 metrics, you typically need to install the Elastic [Amazon S3 inte
 
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
-:::::{dropdown} **Quick guide: Add data**
-::::{note}
+:::::{dropdown} Quick guide: Add data
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon S3** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.

solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md

@@ -113,10 +113,10 @@ To add the integration:
     **Subscription ID**
     :   The subscription ID listed on the main Subscriptions page.
 
-    :::{image} ../../../images/observability-agent-tut-azure-integration-settings.png
-    :alt: Screenshot of integration settings for Azure
-    :class: screenshot
-    :::
+        :::{image} ../../../images/observability-agent-tut-azure-integration-settings.png
+        :alt: Screenshot of integration settings for Azure
+        :class: screenshot
+        :::
 
 6. Make sure the **Collect Azure Billing metrics** selector is turned on.
 7. Accept the defaults to create a new agent policy.
@@ -266,10 +266,10 @@ To add the integration:
     **Storage account key**
     :   A valid access key defined for the storage account.
 
-    :::{image} ../../../images/observability-agent-tut-azure-activity-log-settings.png
-    :alt: Screenshot of integration settings for Azure activity logs
-    :class: screenshot
-    :::
+        :::{image} ../../../images/observability-agent-tut-azure-activity-log-settings.png
+        :alt: Screenshot of integration settings for Azure activity logs
+        :class: screenshot
+        :::
 
 6. Make sure the **Collect Azure activity logs from Event Hub** selector is turned on.
 7. Under **Existing hosts**, select the agent policy that created earlier.

solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md

@@ -139,7 +139,7 @@ The processes listed in the **Top processes** table are based on an aggregation
 
 :::::
 
-:::::{dropdown} **Universal Profiling**
+:::::{dropdown} Universal Profiling
 The **Universal Profiling** tab shows CPU usage down to the application code level. From here, you can find the sources of resource usage, and identify code that can be optimized to reduce infrastructure costs. The Universal Profiling tab has the following views.
 
 |     |     |