Connection pools

Every HTTP connection an agent server opens goes through a connection pool: the calls to Search2o Cloud, the LLM calls, and the calls made by api commands and API profiles. Each of those can name its own pool. Pools are defined on the Connection pools page in the GUI, by administrators, and the pool named default is used wherever no pool is named. A changed pool reaches every agent server before the server's next run, and the old pool stays open until the last agent using the old pool finishes.

Field	Type	Default	Description
`pools`	object of profile name → ApiConnectionPoolModel		The connection pools available to the whole system, keyed by name. The pool named 'default' cannot be deleted.

A pool

Field	Type	Default	Description
`maxConnections`	integer	20	The most connections this pool opens at once.
`maxKeepaliveConnections`	integer	10	The most idle connections kept open for reuse.
`keepaliveExpiry`	integer	60	How long an idle connection is kept before it is closed.
`timeout`	TimeoutModel		The connect, read, write and pool timeouts for calls made through this pool.
`caCertFile`	string		PEM file containing the certificate authority or chain this pool trusts. It REPLACES the authorities trusted by default rather than adding to them, so it must contain every authority this pool needs to reach its endpoint.
`clientCertFile`	string		PEM file containing the client certificate and its chain.
`privateKeyFile`	string		PEM file containing the private key. May be omitted when the private key is included in clientCertFile.
`privateKeyPasswordSecret`	string		Name of the secret that holds the password for the encrypted private key, if required.

Timeouts

Field	Type	Default	Description
`connect`	number	10.0	How long to wait to establish the TCP/TLS connection.
`read`	number	300.0	How long to wait for response bytes.
`write`	number	30.0	How long to wait while sending the request body.
`pool`	number	10.0	How long to wait for a free connection from the pool.