The agent checkin endpoint. Clients will long-poll this endpoint. A client may inform fleet-server of it's long-poll timeout in the request body. The fleet-server will return a response if there is a new action for the agent, or if the polling timeout is reached. The fleet-server may also use some jitter to offset the polling timeout, if specified a random amount of the jitter value may be subtracted from the polling timeout. The fleet-sever polling timeout is short-circuited in cases of heavy load where setting up the checkin (ensuring the API key is authed etc) takes longer then the timeout value. Fleet-server sets the poll timeout to 5m by default (with a 10m write timeout), for these values we assume that elastic-agent's request timeout is set to 10m and the cloud-proxy's timeout is longer than 10m.
Path parameters
The agent ID.
Headers
If the agent is able to accept encoded responses. Used to indicate if GZIP compression may be used by the server. The elastic-agent does not use the accept-encoding header.
The user-agent header that is sent. Must have the format "elastic agent X.Y.Z" where "X.Y.Z" indicates the agent version. The agent version must not be greater than the version of the fleet-server.
The request tracking ID for APM.
The API version to use, format should be "YYYY-MM-DD"
Request body
Response
Agent checkin successful. May include actions.