Add known limitations (#4968) (#4970)

(cherry picked from commit 1bd3c15)

Co-authored-by: Arianna Laudazzi <[email protected]>

Author: mergify[bot]

docs/en/observability/synthetics-private-location.asciidoc

@@ -175,6 +175,17 @@ These limits are for simultaneous tests, not total tests. For example, if
 However, it is a good practice to set up execution slots with extra capacity. A good starting point would be to over-allocate by
 a factor of 5. In the previous example that would mean allocating 5 slots.
 
+[discrete]
+[[synthetics-known-limitations-vertical-scaling]]
+== Known limitations on vertical scaling 
+
+- 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.
+
+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.
+
+
 [discrete]
 [[synthetics-private-location-next]]
 = Next steps