Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.9] Need more clarity for the fleet server scale documentation (backport #383) #387

Merged
merged 1 commit into from
Aug 3, 2023
Merged

[8.9] Need more clarity for the fleet server scale documentation (backport #383) #387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 19 additions & 10 deletions docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

* <<resource-requirements-by-number-agents>>

Expand All @@ -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
Expand Down