fix(lb): add access logs info (#5353)

* fix(lb): add access logs info

* Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

---------

Co-authored-by: Jessica <[email protected]>

Author: RoRoJ

pages/load-balancer/how-to/assets/scaleway-logs-cockpit-overview.webp

@@ -124,7 +124,7 @@ From the Scaleway Cockpit dashboards homepage, click **Dashboards** in the side
 
 At the top of the dashboard, you can configure parameters, which control which logs are displayed. In addition to all the same parameters as for [metrics](#choosing-metric-parameters), you can also **filter** for specific log values, and select the **log level** (`info`, `warning`, `alert`).
 
-### Logged events
+### Event logs
 
 The following events are logged:
 
@@ -150,4 +150,16 @@ Logs when a backend server that was previously inaccessible becomes accessible a
 
 Logs when a frontend's SSL/TLS certificate is about to expire or has expired.
 
+### Access logs
 
+<Message type="tip">
+Access logs are not collected by default. To enable them for a given frontend, use the [Update frontend](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-frontends-update-a-frontend) call in the API, and set the field `enable_access_logs` to `true`. You cannot currently enable access logs via the Scaleway console.
+</Message>
+
+Access logs capture details of incoming network traffic handled by the Load Balancer. Each log is shown in the following format:
+
+```
+<date> <timestamp> <client IP: client port> <frontend name / frontend IP: frontend port> <backend name / backend server IP: backend server port> 
+```
+
+Depending on the protocol, the HTTP request and status code, or, the client SNI, completes the log.