From 747b1a55d2043fc7edd8b91d179158ba4ab3ecf2 Mon Sep 17 00:00:00 2001 From: emilioalvap Date: Wed, 5 Nov 2025 20:54:20 +0100 Subject: [PATCH 1/8] Adjust private location docs to support base elastic-agent image --- reference/fleet/elastic-agent-container.md | 9 ++-- ...ate-from-elastic-synthetics-integration.md | 2 +- .../monitor-resources-on-private-networks.md | 43 +++++++++++++++---- .../synthetics/support-matrix.md | 6 ++- 4 files changed, 43 insertions(+), 17 deletions(-) diff --git a/reference/fleet/elastic-agent-container.md b/reference/fleet/elastic-agent-container.md index fd37fd8ddb..3508ec0d6c 100644 --- a/reference/fleet/elastic-agent-container.md +++ b/reference/fleet/elastic-agent-container.md @@ -69,7 +69,7 @@ docker pull docker.elastic.co/elastic-agent/elastic-agent-wolfi:{{version.stack} ### Complete flavor -If you want to run Synthetics tests, run the docker pull command to fetch the elastic-agent-complete image: +If you want to run Synthetics Browser tests, run the docker pull command to fetch the elastic-agent-complete image: ```terminal subs=true docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} @@ -137,8 +137,7 @@ docker run \ 1. Set to 1 to enroll the {{agent}} into {{fleet-server}}. 2. URL to enroll the {{fleet-server}} into. You can find it in {{kib}}. Select **Management → {{fleet}} → Fleet Settings**, and copy the {{fleet-server}} host URL. 3. The token to use for enrollment. Close the flyout panel and select **Enrollment tokens**. Find the Agent policy you want to enroll {{agent}} into, and display and copy the secret token. To learn how to create a policy, refer to [Create an agent policy without using the UI](/reference/fleet/create-policy-no-ui.md). -4. If you want to run **elastic-agent-complete** image, replace `elastic-agent` to `elastic-agent-complete`. Use the `elastic-agent` user instead of root to run Synthetics Browser tests. Synthetic tests cannot run under the root user. Refer to [Synthetics {{fleet}} Quickstart](/solutions/observability/synthetics/get-started.md) for more information. - +4. Switch `elastic-agent` to `elastic-agent-complete` if you intend to use the complete version. Use the `elastic-agent` user instead of root to run Synthetics Browser tests. Synthetic tests cannot run under the root user. Refer to [Synthetics {{fleet}} Quickstart](/solutions/observability/synthetics/get-started.md) for more information. Refer to [Environment variables](/reference/fleet/agent-environment-variables.md) for all available options. ::: @@ -161,8 +160,7 @@ docker run \ 3. The {{fleet}} service token. [Generate one in the {{fleet}} UI](/reference/fleet/fleet-enrollment-tokens.md#create-fleet-enrollment-tokens) if you don’t have one already. 4. ID of the {{fleet-server}} policy. We recommend only having one fleet-server policy. To learn how to create a policy, refer to [Create an agent policy without using the UI](/reference/fleet/create-policy-no-ui.md). 5. publish container port 8220 to host. -6. If you want to run the **elastic-agent-complete** image, replace `elastic-agent` with `elastic-agent-complete`. Use the `elastic-agent` user instead of root to run Synthetics Browser tests. Synthetic tests cannot run under the root user. Refer to [Synthetics {{fleet}} Quickstart](/solutions/observability/synthetics/get-started.md) for more information. - +6. Switch `elastic-agent` to `elastic-agent-complete` if you intend to use the complete version. Use the `elastic-agent` user instead of root to run Synthetics Browser tests. Synthetic tests cannot run under the root user. Refer to [Synthetics {{fleet}} Quickstart](/solutions/observability/synthetics/get-started.md) for more information. Refer to [Environment variables](/reference/fleet/agent-environment-variables.md) for all available options. ::: @@ -244,7 +242,6 @@ services: - FLEET_ENROLL=1 - FLEET_URL= ``` - 1. Switch `elastic-agent` to `elastic-agent-complete` if you intend to use the complete version. Use the `elastic-agent` user instead of root to run Synthetics Browser tests. Synthetic tests cannot run under the root user. Refer to [Synthetics {{fleet}} Quickstart](/solutions/observability/synthetics/get-started.md) for more information. 2. Synthetic browser monitors require this set to `elastic-agent`. diff --git a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md index 737dbefb6b..87c21e45f4 100644 --- a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md +++ b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md @@ -84,7 +84,7 @@ Find more details in [Use the {{synthetics-app}}](/solutions/observability/synth ## Where monitors run [synthetics-migrate-integration-location] -If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you have already have an {{agent}} running using `elastic-agent-complete`, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). +If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} container running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). Alternatively, you can start hosting on Elastic’s global managed infrastructure. With Elastic’s global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. diff --git a/solutions/observability/synthetics/monitor-resources-on-private-networks.md b/solutions/observability/synthetics/monitor-resources-on-private-networks.md index 8788c1d14d..c471411304 100644 --- a/solutions/observability/synthetics/monitor-resources-on-private-networks.md +++ b/solutions/observability/synthetics/monitor-resources-on-private-networks.md @@ -56,10 +56,9 @@ By default {{private-location}}s are configured to allow two simultaneous browse After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Observability Serverless project and enroll an {{agent}} in {{fleet}}. -Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. For monitors running on {{private-location}}s, you *must* use the `elastic-agent-complete` Docker image to create a self-hosted {{agent}} node. The standard {{ecloud}} or self-hosted {{agent}} will not work. - +Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants, as it includes the required dependencies. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. ::::{important} -The `elastic-agent-complete` Docker image is the only way to have all available options that you see in the UI. +The `elastic-agent` Docker image variants are the only way to have all available options that you see in the UI. :::: @@ -67,31 +66,53 @@ To pull the Docker image run: ::::{tab-set} :group: docker -:::{tab-item} Latest +:::{tab-item} `elastic-agent` :sync: latest ```shell subs=true -docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} +# Supports TCP, ICMP and HTTP monitors +docker pull docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} ``` ::: -:::{tab-item} Specific version +:::{tab-item} `elastic-agent-complete` :sync: specific ```sh subs=true -docker pull docker.elastic.co/elastic-agent/elastic-agent-complete: +# Supports all monitor types: TCP, ICMP, HTTP and Browser +docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} ``` -You can download and install a specific version of the {{stack}} by replacing `` with the version number you want. For example, you can replace `` with {{version.stack.base}}. ::: :::: +You can download and install a specific version of the {{stack}} by replacing `{{version.stack}}` with the version number you want. For example, you can replace `{{version.stack}}` with {{version.stack.base}}. + Then enroll and run an {{agent}}. You’ll need an enrollment token and the URL of the {{fleet-server}}. You can use the default enrollment token for your policy or create new policies and [enrollment tokens](/reference/fleet/fleet-enrollment-tokens.md) as needed. For more information on running {{agent}} with Docker, refer to [Run {{agent}} in a container](/reference/fleet/elastic-agent-container.md). +::::{tab-set} +:group: docker +:::{tab-item} `elastic-agent` +:sync: latest + +```shell subs=true +docker run \ + --env FLEET_ENROLL=1 \ + --env FLEET_URL={fleet_server_host_url} \ + --env FLEET_ENROLLMENT_TOKEN={enrollment_token} \ + --cap-add=NET_RAW \ + --cap-add=SETUID \ + --rm docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} +``` + +::: + +:::{tab-item} `elastic-agent-complete` +:sync: specific ```shell subs=true docker run \ @@ -103,8 +124,12 @@ docker run \ --rm docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} ``` +::: + +:::: + ::::{important} -The `elastic-agent-complete` Docker image requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. +The `elastic-agent`/`elastic-agent-complete` container requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. :::: diff --git a/solutions/observability/synthetics/support-matrix.md b/solutions/observability/synthetics/support-matrix.md index fa337111ba..82c1d4bcf5 100644 --- a/solutions/observability/synthetics/support-matrix.md +++ b/solutions/observability/synthetics/support-matrix.md @@ -41,7 +41,11 @@ There are various components that make up the Synthetics solution, which are sup * Any *inline* or *Zip URL* monitors configured with the beta Synthetics integration prior to 1.0.0, are not supported and will stop running in the future - * Shipped as the `elastic-agent-complete` Docker image + * Shipped as multiple `elastic-agent` Docker image variants: + + * `elastic-agent-complete`, which includes all dependencies required to support browser monitors. + * `elastic-agent` which only supports TCP, HTTP and ICMP monitors. + * Must have a direct connection to {{es}} * Do not configure any ingest pipelines or Logstash output From addaff9fd50a60cd0e4951d2e63a32c7551b0022 Mon Sep 17 00:00:00 2001 From: emilioalvap Date: Wed, 5 Nov 2025 20:59:41 +0100 Subject: [PATCH 2/8] Remove container reference --- .../synthetics/migrate-from-elastic-synthetics-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md index 87c21e45f4..f00cac0655 100644 --- a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md +++ b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md @@ -84,7 +84,7 @@ Find more details in [Use the {{synthetics-app}}](/solutions/observability/synth ## Where monitors run [synthetics-migrate-integration-location] -If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} container running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). +If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). Alternatively, you can start hosting on Elastic’s global managed infrastructure. With Elastic’s global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. From 683f2da9e082537e77fd95fabf661a5bb91f89b5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emilio=20Alvarez=20Pi=C3=B1eiro?= <95703246+emilioalvap@users.noreply.github.com> Date: Thu, 6 Nov 2025 13:02:59 +0100 Subject: [PATCH 3/8] Update solutions/observability/synthetics/support-matrix.md Co-authored-by: Luca Belluccini --- solutions/observability/synthetics/support-matrix.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/synthetics/support-matrix.md b/solutions/observability/synthetics/support-matrix.md index 82c1d4bcf5..8aff9cf6e4 100644 --- a/solutions/observability/synthetics/support-matrix.md +++ b/solutions/observability/synthetics/support-matrix.md @@ -43,7 +43,7 @@ There are various components that make up the Synthetics solution, which are sup * Shipped as multiple `elastic-agent` Docker image variants: - * `elastic-agent-complete`, which includes all dependencies required to support browser monitors. + * `elastic-agent-complete`, which includes all dependencies required to run browser monitors, TCP, HTTP and ICMP monitors. * `elastic-agent` which only supports TCP, HTTP and ICMP monitors. * Must have a direct connection to {{es}} From b4019b742f137b1239ca657abfa13d720c8dcf39 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emilio=20Alvarez=20Pi=C3=B1eiro?= <95703246+emilioalvap@users.noreply.github.com> Date: Thu, 6 Nov 2025 13:05:11 +0100 Subject: [PATCH 4/8] Update solutions/observability/synthetics/monitor-resources-on-private-networks.md Co-authored-by: Luca Belluccini --- .../synthetics/monitor-resources-on-private-networks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/synthetics/monitor-resources-on-private-networks.md b/solutions/observability/synthetics/monitor-resources-on-private-networks.md index c471411304..1e7eabb0ef 100644 --- a/solutions/observability/synthetics/monitor-resources-on-private-networks.md +++ b/solutions/observability/synthetics/monitor-resources-on-private-networks.md @@ -129,7 +129,7 @@ docker run \ :::: ::::{important} -The `elastic-agent`/`elastic-agent-complete` container requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. +The `elastic-agent`/`elastic-agent-complete` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. :::: From 623f45d9eba88e89ce5bbdd41e709b93d97bb167 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emilio=20Alvarez=20Pi=C3=B1eiro?= <95703246+emilioalvap@users.noreply.github.com> Date: Thu, 6 Nov 2025 17:49:54 +0100 Subject: [PATCH 5/8] Update reference/fleet/elastic-agent-container.md Co-authored-by: Luca Belluccini --- reference/fleet/elastic-agent-container.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/reference/fleet/elastic-agent-container.md b/reference/fleet/elastic-agent-container.md index 3508ec0d6c..2ab9b8b36c 100644 --- a/reference/fleet/elastic-agent-container.md +++ b/reference/fleet/elastic-agent-container.md @@ -69,7 +69,9 @@ docker pull docker.elastic.co/elastic-agent/elastic-agent-wolfi:{{version.stack} ### Complete flavor -If you want to run Synthetics Browser tests, run the docker pull command to fetch the elastic-agent-complete image: +In case you need to run {{agent}} as a Synthetic Private Location and you'll use only Lightweight monitors, you can use the `elastic-agent` (and the `wolfi` variant). + + In case you need to run {{agent}} as a Synthetic Private Location and you'll use both Lightweight monitors and Synthetics Browser tests, run the docker pull command to fetch the `elastic-agent-complete` image: ```terminal subs=true docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} From 315807a08504607fdf9f8891894cf8012563a297 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emilio=20Alvarez=20Pi=C3=B1eiro?= <95703246+emilioalvap@users.noreply.github.com> Date: Thu, 6 Nov 2025 17:51:38 +0100 Subject: [PATCH 6/8] Apply suggestions from code review Co-authored-by: Luca Belluccini --- .../migrate-from-elastic-synthetics-integration.md | 6 +++++- .../synthetics/monitor-resources-on-private-networks.md | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md index f00cac0655..8d4ef3b6ae 100644 --- a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md +++ b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md @@ -84,7 +84,11 @@ Find more details in [Use the {{synthetics-app}}](/solutions/observability/synth ## Where monitors run [synthetics-migrate-integration-location] -If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). +If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. + +Only the `elastic-agent-complete` image (and its `wolfi` variant) allows to run Synthetic Browser tests. + +To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). Alternatively, you can start hosting on Elastic’s global managed infrastructure. With Elastic’s global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. diff --git a/solutions/observability/synthetics/monitor-resources-on-private-networks.md b/solutions/observability/synthetics/monitor-resources-on-private-networks.md index 1e7eabb0ef..de3f61ea5b 100644 --- a/solutions/observability/synthetics/monitor-resources-on-private-networks.md +++ b/solutions/observability/synthetics/monitor-resources-on-private-networks.md @@ -58,7 +58,7 @@ After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants, as it includes the required dependencies. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. ::::{important} -The `elastic-agent` Docker image variants are the only way to have all available options that you see in the UI. +The `elastic-agent-complete` Docker image is the only way to have all available options that you see in the UI. You can use `elastic-agent` Docker image only in case you will only use lightweight monitors. :::: From 9c819c9e625c50d12e4fb6de10d90c0e7b9b4d78 Mon Sep 17 00:00:00 2001 From: emilioalvap Date: Thu, 6 Nov 2025 18:36:14 +0100 Subject: [PATCH 7/8] reorg docs --- ...ate-from-elastic-synthetics-integration.md | 3 ++ .../monitor-resources-on-private-networks.md | 47 ++++++++++--------- .../synthetics/support-matrix.md | 4 +- 3 files changed, 31 insertions(+), 23 deletions(-) diff --git a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md index 8d4ef3b6ae..8f0d5f6ac7 100644 --- a/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md +++ b/solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md @@ -86,8 +86,11 @@ Find more details in [Use the {{synthetics-app}}](/solutions/observability/synth If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}. +::::{note} Only the `elastic-agent-complete` image (and its `wolfi` variant) allows to run Synthetic Browser tests. +:::: + To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). Alternatively, you can start hosting on Elastic’s global managed infrastructure. With Elastic’s global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. diff --git a/solutions/observability/synthetics/monitor-resources-on-private-networks.md b/solutions/observability/synthetics/monitor-resources-on-private-networks.md index de3f61ea5b..ea3bd3785b 100644 --- a/solutions/observability/synthetics/monitor-resources-on-private-networks.md +++ b/solutions/observability/synthetics/monitor-resources-on-private-networks.md @@ -56,9 +56,9 @@ By default {{private-location}}s are configured to allow two simultaneous browse After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Observability Serverless project and enroll an {{agent}} in {{fleet}}. -Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants, as it includes the required dependencies. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. +Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily, additional installation methods can be found on the [{{agent}} installation guide](/reference/fleet/install-elastic-agents.md). ::::{important} -The `elastic-agent-complete` Docker image is the only way to have all available options that you see in the UI. You can use `elastic-agent` Docker image only in case you will only use lightweight monitors. +For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants in a containerized environment, as it includes the required dependencies. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. :::: @@ -66,16 +66,6 @@ To pull the Docker image run: ::::{tab-set} :group: docker -:::{tab-item} `elastic-agent` -:sync: latest - -```shell subs=true -# Supports TCP, ICMP and HTTP monitors -docker pull docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} -``` - -::: - :::{tab-item} `elastic-agent-complete` :sync: specific @@ -86,6 +76,16 @@ docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.sta ::: +:::{tab-item} `elastic-agent` +:sync: latest + +```shell subs=true +# Supports TCP, ICMP and HTTP monitors +docker pull docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} +``` + +::: + :::: You can download and install a specific version of the {{stack}} by replacing `{{version.stack}}` with the version number you want. For example, you can replace `{{version.stack}}` with {{version.stack.base}}. @@ -96,8 +96,8 @@ For more information on running {{agent}} with Docker, refer to [Run {{agent}} i ::::{tab-set} :group: docker -:::{tab-item} `elastic-agent` -:sync: latest +:::{tab-item} `elastic-agent-complete` +:sync: specific ```shell subs=true docker run \ @@ -106,13 +106,18 @@ docker run \ --env FLEET_ENROLLMENT_TOKEN={enrollment_token} \ --cap-add=NET_RAW \ --cap-add=SETUID \ - --rm docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} + --rm docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} ``` +::::{important} +The `elastic-agent-complete` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. + +:::: + ::: -:::{tab-item} `elastic-agent-complete` -:sync: specific +:::{tab-item} `elastic-agent` +:sync: latest ```shell subs=true docker run \ @@ -121,15 +126,15 @@ docker run \ --env FLEET_ENROLLMENT_TOKEN={enrollment_token} \ --cap-add=NET_RAW \ --cap-add=SETUID \ - --rm docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} + --rm docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} ``` -::: +::::{important} +The `elastic-agent` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. :::: -::::{important} -The `elastic-agent`/`elastic-agent-complete` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. +::: :::: diff --git a/solutions/observability/synthetics/support-matrix.md b/solutions/observability/synthetics/support-matrix.md index 8aff9cf6e4..12fea61d48 100644 --- a/solutions/observability/synthetics/support-matrix.md +++ b/solutions/observability/synthetics/support-matrix.md @@ -41,9 +41,9 @@ There are various components that make up the Synthetics solution, which are sup * Any *inline* or *Zip URL* monitors configured with the beta Synthetics integration prior to 1.0.0, are not supported and will stop running in the future - * Shipped as multiple `elastic-agent` Docker image variants: + * Shipped as multiple `elastic-agent` variants: - * `elastic-agent-complete`, which includes all dependencies required to run browser monitors, TCP, HTTP and ICMP monitors. + * `elastic-agent-complete`, exclusively provided as a Docker image which includes all dependencies required to run browser, TCP, HTTP and ICMP monitors. * `elastic-agent` which only supports TCP, HTTP and ICMP monitors. * Must have a direct connection to {{es}} From 3f4668b6958894dce3cabf634caa6bc77dd8324f Mon Sep 17 00:00:00 2001 From: emilioalvap Date: Thu, 6 Nov 2025 20:48:13 +0100 Subject: [PATCH 8/8] Fix formatting --- .../monitor-resources-on-private-networks.md | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/solutions/observability/synthetics/monitor-resources-on-private-networks.md b/solutions/observability/synthetics/monitor-resources-on-private-networks.md index ea3bd3785b..2a3370abea 100644 --- a/solutions/observability/synthetics/monitor-resources-on-private-networks.md +++ b/solutions/observability/synthetics/monitor-resources-on-private-networks.md @@ -56,9 +56,9 @@ By default {{private-location}}s are configured to allow two simultaneous browse After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Observability Serverless project and enroll an {{agent}} in {{fleet}}. -Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily, additional installation methods can be found on the [{{agent}} installation guide](/reference/fleet/install-elastic-agents.md). +Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. Additional installation methods can be found on the [{{agent}} installation guide](/reference/fleet/install-elastic-agents.md). ::::{important} -For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants in a containerized environment, as it includes the required dependencies. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. +For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants in a containerized environment. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors. :::: @@ -66,7 +66,7 @@ To pull the Docker image run: ::::{tab-set} :group: docker -:::{tab-item} `elastic-agent-complete` +:::{tab-item} elastic-agent-complete :sync: specific ```sh subs=true @@ -76,7 +76,7 @@ docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.sta ::: -:::{tab-item} `elastic-agent` +:::{tab-item} elastic-agent :sync: latest ```shell subs=true @@ -96,7 +96,7 @@ For more information on running {{agent}} with Docker, refer to [Run {{agent}} i ::::{tab-set} :group: docker -:::{tab-item} `elastic-agent-complete` +:::{tab-item} elastic-agent-complete :sync: specific ```shell subs=true @@ -109,14 +109,11 @@ docker run \ --rm docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}} ``` -::::{important} The `elastic-agent-complete` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. -:::: - ::: -:::{tab-item} `elastic-agent` +:::{tab-item} elastic-agent :sync: latest ```shell subs=true @@ -129,11 +126,8 @@ docker run \ --rm docker.elastic.co/elastic-agent/elastic-agent:{{version.stack}} ``` -::::{important} The `elastic-agent` container, when running as Synthetics Private Locations, requires additional capabilities to operate correctly. Ensure `NET_RAW` and `SETUID` are enabled on the container. -:::: - ::: ::::