From 83df57c3fb0cc7c23d1cc91f0a8259679c5d6a09 Mon Sep 17 00:00:00 2001 From: nima Date: Thu, 3 Aug 2023 23:45:40 +1000 Subject: [PATCH] Need more clarity for the fleet server scale documentation (#383) * Need more clarity for the fleet server scale documentation ... as it is raising questions from the field. * Update docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc --------- Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> (cherry picked from commit 7a060484140e881cc62521dea56c1f4dcac48018) --- .../fleet/fleet-server-scaling.asciidoc | 29 ++++++++++++------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc b/docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc index 36fce3bc7..4ca818303 100644 --- a/docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc +++ b/docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc @@ -188,8 +188,10 @@ Maximum size in bytes of the uploadChunk API request body. [[scaling-recommendations]] == Scaling recommendations ({ecloud}) -The following tables provide resource requirements and scaling guidelines based -on the number of agents required by your deployment: +The following tables provide the minimum resource requirements and scaling guidelines based +on the number of agents required by your deployment. It should be noted that these compute +resource can be spread across multiple availability zones (for example: a 32GB RAM requirement +can be satisfed with 16GB of RAM in 2 different zones). * <> @@ -198,16 +200,23 @@ on the number of agents required by your deployment: === Resource requirements by number of agents |=== | Number of Agents | {fleet-server} Memory | {fleet-server} vCPU | {es} Hot Tier -| 2,000 | 2GB | up to 8 vCPU | 16GB x2 RAM \| 4 vCPU x2 -| 5,000 | 4GB | up to 8 vCPU | 16GB x2 RAM \| 4 vCPU x2 -| 10,000 | 8GB | up to 8 vCPU | 64GB x2 RAM \| 16 vCPU x2 -| 15,000 | 8GB | up to 8 vCPU | 128GB x2 RAM \| 32 vCPU x2 -| 25,000 | 8GB | up to 8 vCPU | 128GB x2 RAM \| 32 vCPU x2 -| 50,000 | 8GB | up to 8 vCPU | 192GB x2 RAM \| 48 vCPU x2 -| 75,000 | 8GB | up to 8 vCPU | 192GB x2 RAM \| 48 vCPU x2 -| 100,000 | 8GB x2 | 8 vCPU x2 | 256GB x2 RAM \| 64 vCPU x2 +| 2,000 | 2GB | up to 8 vCPU | 32GB RAM \| 8 vCPU +| 5,000 | 4GB | up to 8 vCPU | 32GB RAM \| 8 vCPU +| 10,000 | 8GB | up to 8 vCPU | 128GB RAM \| 32 vCPU +| 15,000 | 8GB | up to 8 vCPU | 256GB RAM \| 64 vCPU +| 25,000 | 8GB | up to 8 vCPU | 256GB RAM \| 64 vCPU +| 50,000 | 8GB | up to 8 vCPU | 384GB RAM \| 96 vCPU +| 75,000 | 8GB | up to 8 vCPU | 384GB RAM \| 96 vCPU +| 100,000 | 16GB | 16 vCPU | 512GB RAM \| 128 vCPU |=== +A series of scale performance tests are regularly executed in order to verify the above requirements +and the ability for {fleet} to manage the advertised scale of {agent}s. These tests go through a set +of acceptance criteria. The criteria mimics a typical platform operator workflow. The test cases are +performing agent installations, version upgrades, policy modifications, and adding/removing integrations, +tags, and policies. Acceptance criteria is passed when the {agent}s reach a `Healthy` state after any +of these operations. + [discrete] [[agent-policy-scaling-recommendations]] == Policy scaling recommendations