> For the complete documentation index, see [llms.txt](https://doc.flow.swiss/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.flow.swiss/products/compute/networking/load-balancers/managing-balancing-pools.md). # Balancing Pools ## Manage the Balancing Pools A load balancer can have one or more balancing pools. The balancing and health monitor properties are defined in the balancing pools. To see a list of balancing pools of a load balancer, click on its name. To edit the balancing settings (such as the balancing algorithm and session persistence) or health monitor parameters, click the properties icon in the right corner. You can monitor its performance and health on the Status, see its parameters on the Properties, and manage its members on the Members tab. ## Members Each balancing pool contains one or more members (instances). The traffic is redirected to these using the configured balancing algorithm. To view the members to a balancing pool, click its name. You have the possibility to add, disable and remove members at runtime. ## Health Monitor A health monitor is a scheduled HTTP, TCP, UDP Connect or ICMP request that you can configure to run on a repeating basis to ensure that a service is healthy. You can manually set the health monitor parameters in the Balancers Detail view. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.flow.swiss/products/compute/networking/load-balancers/managing-balancing-pools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.