From 24c1f257e2e4745fb39b4a119f77d83ab246afc5 Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi Date: Wed, 13 May 2026 09:48:31 +0200 Subject: [PATCH 1/2] Port fix from 9.0 --- docs/en/observability/synthetics-private-location.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/observability/synthetics-private-location.asciidoc b/docs/en/observability/synthetics-private-location.asciidoc index 0ddb028a4b..dd30663fa7 100644 --- a/docs/en/observability/synthetics-private-location.asciidoc +++ b/docs/en/observability/synthetics-private-location.asciidoc @@ -181,7 +181,7 @@ a factor of 5. In the previous example that would mean allocating 5 slots. - A single private location will not scale beyond 10,000 monitors. Exceeding this number will result in agent degradation and inconsistent execution, regardless of the resources allocated. -- Complex monitor configuration can disproportionately increase the private location policy size, leading to agent communication errors and degradation even if the limit mentioned above hasn't been reached. In these edge cases, increasing the `server.limits.checkin_limit.max_body_byte_size` setting on Fleet Server to 8 MB or 16 MB (or setting it to -1 to turn off the limit entirely) might help prevent communication errors. +- Many Synthetics monitors, or monitors with complex configurations, can cause the check-in payload to exceed the default 1 MiB `checkin_limit.max_body_byte_size` limit on {fleet-server}. When this happens, check-ins are rejected and agents appear offline or unhealthy in the Fleet UI even though monitors are executing successfully. To resolve this, increase the `server.limits.checkin_limit.max_body_byte_size` setting on your self-managed {fleet-server}. If you're facing one of these scenarios, it is likely that the private location has grown too large and needs to be split into smaller locations, each alloted a portion of the original location monitors. From 3658808ccb7166cfcfa8190c6ec3c3f3e6812e62 Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi Date: Wed, 13 May 2026 10:36:29 +0200 Subject: [PATCH 2/2] Add reference to fleet docs --- docs/en/observability/synthetics-private-location.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/observability/synthetics-private-location.asciidoc b/docs/en/observability/synthetics-private-location.asciidoc index dd30663fa7..7be1649e41 100644 --- a/docs/en/observability/synthetics-private-location.asciidoc +++ b/docs/en/observability/synthetics-private-location.asciidoc @@ -181,7 +181,7 @@ a factor of 5. In the previous example that would mean allocating 5 slots. - A single private location will not scale beyond 10,000 monitors. Exceeding this number will result in agent degradation and inconsistent execution, regardless of the resources allocated. -- Many Synthetics monitors, or monitors with complex configurations, can cause the check-in payload to exceed the default 1 MiB `checkin_limit.max_body_byte_size` limit on {fleet-server}. When this happens, check-ins are rejected and agents appear offline or unhealthy in the Fleet UI even though monitors are executing successfully. To resolve this, increase the `server.limits.checkin_limit.max_body_byte_size` setting on your self-managed {fleet-server}. +- Many Synthetics monitors, or monitors with complex configurations, can cause the check-in payload to exceed the default 1 MiB `checkin_limit.max_body_byte_size` limit on {fleet-server}. When this happens, check-ins are rejected and agents appear offline or unhealthy in the Fleet UI even though monitors are executing successfully. To resolve this, increase the `server.limits.checkin_limit.max_body_byte_size` setting on your self-managed {fleet-server}. Refer to the {fleet-guide}/fleet-server-scalability.html[Advanced {fleet-server} options] documentation for configuration details and an example. If you're facing one of these scenarios, it is likely that the private location has grown too large and needs to be split into smaller locations, each alloted a portion of the original location monitors.