Skip to content
Merged
Changes from all commits
Commits
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
27 changes: 18 additions & 9 deletions docs/en/ingest-management/fleet/fleet-server-scaling.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,16 @@ Burst of check-ins allowed before falling back to the rate defined by
`interval`.

`checkin_limit.max_body_byte_size`:::
Maximum size in bytes of the checkin API request body.
Maximum size in bytes of the checkin API request body. Defaults to `1048576` bytes (1 MiB). Deployments running many Synthetics monitors might need to increase this value to avoid check-in failures that cause agents to appear offline or unhealthy in the {fleet} UI despite monitors executing successfully. For example:
+
[source,yaml]
----
server:
limits:
max_body_byte_size: 104857600
checkin_limit:
max_body_byte_size: 104857600
----

`artifact_limit.max`:::
Maximum number of agents that can call the artifact API concurrently. It allows
Expand Down Expand Up @@ -146,10 +155,10 @@ Burst of enrollments to accept before falling back to the rate defined by
Maximum size in bytes of the enroll API request body.

`status_limit.max`:::
Maximum number of agents that can call the status API concurrently. This setting allows the user to avoid overloading the Fleet Server from status API calls.
Maximum number of agents that can call the status API concurrently. This setting allows the user to avoid overloading the {fleet-server} from status API calls.

`status_limit.interval`:::
How frequently agents can submit status requests to the Fleet Server.
How frequently agents can submit status requests to the {fleet-server}.

`status_limit.burst`:::
Burst of status requests to accomodate before falling back to the rate defined by interval.
Expand All @@ -158,10 +167,10 @@ Burst of status requests to accomodate before falling back to the rate defined b
Maximum size in bytes of the status API request body.

`upload_start_limit.max`:::
Maximum number of agents that can call the uploadStart API concurrently. This setting allows the user to avoid overloading the Fleet Server from uploadStart API calls.
Maximum number of agents that can call the uploadStart API concurrently. This setting allows the user to avoid overloading the {fleet-server} from uploadStart API calls.

`upload_start_limit.interval`:::
How frequently agents can submit file start upload requests to the Fleet Server.
How frequently agents can submit file start upload requests to the {fleet-server}.

`upload_start_limit.burst`:::
Burst of file start upload requests to accomodate before falling back to the rate defined by interval.
Expand All @@ -170,10 +179,10 @@ Burst of file start upload requests to accomodate before falling back to the rat
Maximum size in bytes of the uploadStart API request body.

`upload_end_limit.max`:::
Maximum number of agents that can call the uploadEnd API concurrently. This setting allows the user to avoid overloading the Fleet Server from uploadEnd API calls.
Maximum number of agents that can call the uploadEnd API concurrently. This setting allows the user to avoid overloading the {fleet-server} from uploadEnd API calls.

`upload_end_limit.interval`:::
How frequently agents can submit file end upload requests to the Fleet Server.
How frequently agents can submit file end upload requests to the {fleet-server}.

`upload_end_limit.burst`:::
Burst of file end upload requests to accomodate before falling back to the rate defined by interval.
Expand All @@ -182,10 +191,10 @@ Burst of file end upload requests to accomodate before falling back to the rate
Maximum size in bytes of the uploadEnd API request body.

`upload_chunk_limit.max`:::
Maximum number of agents that can call the uploadChunk API concurrently. This setting allows the user to avoid overloading the Fleet Server from uploadChunk API calls.
Maximum number of agents that can call the uploadChunk API concurrently. This setting allows the user to avoid overloading the {fleet-server} from uploadChunk API calls.

`upload_chunk_limit.interval`:::
How frequently agents can submit file chunk upload requests to the Fleet Server.
How frequently agents can submit file chunk upload requests to the {fleet-server}.

`upload_chunk_limit.burst`:::
Burst of file chunk upload requests to accomodate before falling back to the rate defined by interval.
Expand Down