[Website]: When using elevated number of Synthetic monitors on a single private location, we might point to bump the Fleet Server check-in limit #2929
Description
Type of issue
None
What documentation page is affected
https://www.elastic.co/docs/solutions/observability/synthetics/monitor-resources-on-private-networks
What happened?
When using elevated number of Synthetic monitors on a single private location, we might point to bump the Fleet Server check-in limit.
The symptom is the Elastic Agent will report in the Status (on the elastic-agent status):
status code: 400, fleet-server returned an error: BadRequest, message: Bad request: unable to decode checkin request: http: request body too large
If it is the case, it might be necessary to change the server.limits.checkin_limit.max_body_byte_size on Fleet Server to 8MB or 16MB or eventually -1 (to disable the limit).
Additional info
No response