fix(lb): finish load info

Author: RoRoJ

pages/load-balancer/concepts.mdx

@@ -144,6 +144,15 @@ See [balancing-methods](#balancing-methods).
 
 [Load Balancers](/load-balancer/how-to/create-load-balancer/) are highly available and fully managed instances that allow you to distribute workload across multiple servers. They ensure the scaling of all your applications while securing their continuous availability, even in the event of heavy traffic. They are commonly used to improve the performance and reliability of websites, applications, databases and other services.
 
+## Maximum connections
+
+`Maximum connections` is a parameter that defines the maximum number of simultaneous requests (for HTTP) or simultaneous connections (for TCP) permitted for a single Load Balancer. The value depends on the Load Balancer type:
+
+- **LB-S**: 20,000
+- **LB-M**: 50,000
+- **LB-L**: 160,000
+- **LB-XL**: 3 million 
+
 ## Private Load Balancer
 
 A Load Balancer is defined as private when you choose the "private" [accessibility](#accessibility) option during Load Balancer creation. A Private Load Balancer has no public IP address, and only listens to requests or connections sent through the Private Network(s) to which it is attached. Read more about private Load Balancers and their characteristics and limitations in our [dedicated documentation](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers).

pages/load-balancer/how-to/assets/scaleway-loadbalancer-params.webp

@@ -3,13 +3,12 @@ title: How to monitor your Load Balancer with Scaleway Cockpit
 description: Learn how to efficiently monitor your Scaleway Load Balancer using the intuitive Cockpit dashboard. Enhance your network performance with this step-by-step guide.
 tags: load-balancer cockpit observability dashboard metrics logs alerts
 dates:
-  validation: 2025-10-27
+  validation: 2025-11-06
   posted: 2023-08-07
 ---
 import Requirements from '@macros/iam/requirements.mdx'
 
 import image from './assets/scaleway-lb-dashboard.webp'
-import image2 from './assets/scaleway-loadbalancer-params.webp'
 import image3 from './assets/scaleway-loadbalancer-status.webp'
 import image4 from './assets/scaleway-lb-throughputs.webp'
 import image5 from './assets/scaleway-lb-active-connections.webp'
@@ -51,28 +50,16 @@ From the Scaleway Cockpit dashboards homepage, click **Dashboards** in the side
 
     <Lightbox image={image} alt="" />
 
-### Choosing metric parameters
-
-At the top of the dashboard, you can configure the following parameters, which control which metrics are displayed:
-
-    <Lightbox image={image2} alt="" />
-
-- **A: Time period**: Click this drop-down to configure the time period you want the metrics displayed to cover. You can set an absolute time range, from one fixed date-time to another, or use a quick range such as `Last 15 minutes` or `Last 3 hours`.
-- **B: Refresh rate**: Use the arrow icon to refresh the dashboard, and/or use the drop-down next to it to set the automatic refresh rate.
-- **C: Load Balancer name**: Click this drop-down to select which of your Load Balancers you want to display metrics for.
-- **D: Frontend name**: Click this drop-down to select which of your Load Balancer's frontends you want to display metrics for. You can select all attached frontends, or limit the display to only certain frontends.
-- **E: Backend name**: Click this drop-down to select which of your Load Balancer's backends you want to display metrics for. You can select all attached backends, or limit the display to only certain backends.
-
 ### Load Balancer load
 
-In this section, you can see various graphs which report on the Load Balancer's load and resource usage.
+In this section, you can see various graphs which report on the Load Balancer's **current** load and resource usage.
 
     <Lightbox image={image11} alt="Scaleway Cockpit shows graphs for CPU usage, memory usage, connection usage and bandiwdth in-out usage" />
 
-- **CPU usage**: Shows the percentage of CPU resources utilized by the Load Balancer.
-- **Memory usage**: Shows the percentage of RAM used by the Load Balancer.
-- **Connection usage**: Shows the percentage of maximum concurrent connections currently in use by the Load Balancer.
-- **Bandwidth usage**: Shows the percentage of allocated bandwidth capacity being used by the Load Balancer (inbound and outbound).
+- **CPU usage**: Shows the percentage of available CPU resources currently utilized by the Load Balancer.
+- **Memory usage**: Shows the percentage of available RAM currently used by the Load Balancer.
+- **Connection usage**: Shows the percentage of [maximum concurrent connections](/load-balancer/concepts/#maximum-connections) currently used by the Load Balancer.
+- **Bandwidth usage**: Shows the percentage of allocated bandwidth capacity currently being used by the Load Balancer (inbound and outbound).
 
 ### Load Balancer status
 

pages/load-balancer/how-to/monitor-lb-cockpit.mdx

@@ -125,7 +125,7 @@ A **Limit backend load** toggle displays in the Backend protection screen.
 
   - **Max simultaneous**: Defines the maximum number of simultaneous requests (for HTTP) or simultaneous connections (for TCP) to any single backend server. A value of 20 means that each backend server will have a limit of 20 connections (even if, for example, there are only three servers in the backend). This setting is particularly relevant when using the [First available](#balancing-method) balancing method. 
 
-      The minimum value for this field is 1, and the maximum value depends on the Load Balancer type. You should choose an appropriate value based on your backend server characteristics and traffic patterns.
+      The minimum value for this field is 1, and the maximum value [depends on the Load Balancer type](/load-balancer/concepts/#maximum-connections). You should choose an appropriate value based on your backend server characteristics and traffic patterns.
 
       When the maximum number of simultaneous connections/requests is reached for a single backend server, the Load Balancer will either:
       - Pass the request/connection to a different backend server that still has slots available, unless no backend server has available slots in which case the Load Balancer indicates to the client that the request cannot be handled (e.g. `503 service unavailable` for HTTP or connection closed for TCP), or