---
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: 2026-01-21
  posted: 2023-08-07
---
import Requirements from '@macros/iam/requirements.mdx'
import CockpitIamPermissions from '@macros/cockpit/iam-permissions-cockpit.mdx'

import image from './assets/scaleway-lb-dashboard.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'
import image6 from './assets/scaleway-lb-layer7.webp'
import image7 from './assets/scaleway-logs-cockpit-overview.webp'
import image8 from './assets/scaleway-backend-server-down.webp'
import image9 from './assets/scaleway-backend-down.webp'
import image10 from './assets/scaleway-backend-server-up.webp'
import image11 from './assets/scaleway-lb-load-cockpit.webp'


You can view your Load Balancer's metrics and logs by using [Scaleway Cockpit](/cockpit/quickstart/). Load Balancer is fully integrated into Cockpit, and allows you to monitor your Load Balancers frontends, backends, and backend servers at a glance, and visualize your metrics, traffic and logs. This page explains how to get started with Scaleway Cockpit for viewing your Load Balancers metrics and logs.

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/)

<CockpitIamPermissions />

## How to access the Grafana dashboard

1. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Access Grafana** in the top right corner.

2. Log in to Grafana.

    You are directed to the Scaleway Cockpit dashboards homepage.

## How to view and understand your Load Balancer metrics

From the Scaleway Cockpit dashboards homepage, click **Dashboards** in the side menu, and select **LB Overview** in the **Scaleway** folder.

    You are directed to the Load Balancer Overview dashboard.

    <Lightbox image={image} alt="" />

### Load Balancer load

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 bandwidth in-out usage" />

- **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

In this section, you see various graphs which report on the status of different components of your Load Balancer.

    <Lightbox image={image3} alt="" />

- **Healthy loadbalancer backends**: Shows how many of your Load Balancer's backends currently have a healthy status. A backend is considered healthy if at least one of its [backend servers](/load-balancer/concepts/#backend-servers) is healthy and up.
- **Healthy loadbalancer backend servers**: Shows how many of your Load Balancer's backend servers are currently in a healthy state. A backend server is considered healthy if it passes its [health checks](/load-balancer/concepts/#health-checks), specifically if the number of failed health checks does not exceed the value set in the `Unhealthy threshold` parameter.
- **Backend servers health check**: Shows, for each backend server identified by its IP address and the name of the frontend it is attached to, its current status (`up` (i.e. healthy), or `down` (unhealthy)).
- **"Backend name" health check**: Shows, for each backend identified by its name, how many of its backend servers are currently in a healthy state.

### Backend and frontend delivered/received throughputs

In this section, you see various graphs detailing the delivered and received throughput for your Load Balancer. That is to say, you see the amount of data passing through its frontends, backends, and backend servers.

    <Lightbox image={image4} alt="" />

<Message type="tip">
In these graphs, negative numbers represent sent/outgoing data, while positive numbers represent received/incoming data.
</Message>

- **Frontend throughput bits per seconds**: Data is reported for each frontend (in the example above, for two frontends called `http` and `https`). The total combined data is also shown. In each case, the graph shows the data **received** (from clients) and **sent** (to the backend).
- **Backend throughput bits per seconds**: Data is reported for each backend (in the example above, for three backends called `admin`, `growth-api` and `proxy`). The total combined data is also shown. In each case, the graph shows the data **received** (from the frontend) and **sent** (to the backend server).
- **Backend server throughput bits per seconds**: Data is reported for each backend server, identified by its IP address and the backend it is attached to. The total combined data is also shown. In each case, the graph shows the data **received** and **sent**.

### Active connections

In this section, you see various graphs detailing the current number of active connections for your Load Balancer.

<Message type="note">
This section concerns connections over TCP protocol. However, in the case of a Load Balancer configured to use HTTP protocol, its data will still be reported here (as well as the Layer 7 section below) as the HTTP/HTTPS protocols are included within TCP protocol.
</Message>

    <Lightbox image={image5} alt="" />

- For each frontend, backend and backend server, you can view:
  - The number of current open connections.
  - The rate of new connections (i.e. the number of new connections, as opposed to pre-established connections, per second)


### Layer 7

In this section, you see various graphs detailing the layer 7 (application layer) actions of your Load Balancer.

    <Lightbox image={image6} alt="" />

- For each frontend, backend and backend server, you can view:
  - The HTTP request rate
  - The HTTP response rate per status code

## How to view and understand your Load Balancer logs

From the Scaleway Cockpit dashboards homepage, click **Dashboards** in the side menu, and select **LB Logs Overview**.

    You are directed to the Load Balancer Logs Overview dashboard.

    <Lightbox image={image7} alt="" />

### Choosing log parameters

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](#how-to-view-and-understand-your-load-balancer-metrics), you can also **filter** for specific log values, and select the **log level** (`info`, `warning`, `alert`).

### Event logs

The following events are logged:

#### Backend server down

Logs when a backend server becomes inaccessible.

    <Lightbox image={image8} alt="" />

#### Backend down

Logs when all the backend servers of a backend become inaccessible.

    <Lightbox image={image9} alt="" />

#### Backend server up

Logs when a backend server that was previously inaccessible becomes accessible again.

    <Lightbox image={image10} alt="" />

#### Certificate expired

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.