# Monitoring load balancers

Watch a load balancer's live numbers, read its access log, and receive events about its certificates and its web ACL.

Live numbers and access logs come from the Deutsche Cloud fleet, so `application` and `dedicated`
load balancers have them and `lb11`–`lb31` do not.

## Prerequisites

- Permission for `lb:DescribeLoadBalancers` on the load balancer.
- For the access log, also `monitoring:FilterLogEvents`.

## Live numbers

**Console**
1. Open **Load balancers**, open the load balancer, then the **Live** tab.

The tab refreshes every 5 seconds. It shows one machine's numbers: the active machine's (on a
private `dedicated` load balancer, where both machines serve, one of the two). That is its counters
since it started, with per-second rates from its second report (machines report every 10
seconds); the web ACL's counters when one is attached; and each target's health as that machine
checks it (by target group on `application`, by port on `dedicated`). Last comes the list of the
fleet's machines with their role and state.

**CLI**
```sh
dcloud lb load-balancers live lb-id
```

**API**
```http
GET /lb/api/load-balancers/lb-id/live
```

`400` on `lb11`–`lb31`.

On `application` the counters include requests, 2xx, 4xx and 5xx answers, requests throttled with
`429`, refused connections, misdirected requests (`421`), TLS handshakes and bytes. On `dedicated`
they are connections, connections refused at the cap or the rate, and bytes in and out.

## Access log

One line per request (`application`), or per connection or request (`dedicated`): client, target,
timings and bytes, and on `application` also host, path, status and target group. About 20 lines
a second are stored per load balancer, error lines first; lines are kept 7 days.

Read it on the load balancer's **Access log** tab, or under **Monitoring** in the logs (resource
type `load_balancer`). See [Monitoring](/docs/monitoring).

## Events and metrics

| What                                                            | Where                                                                                           |
| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| A certificate Deutsche Cloud issues could not be issued or renewed | events `Certificate Issuance Failed`, `Certificate Renewal Failed` (source `ews.lb`)            |
| The web ACL blocked or rate-limited requests (per minute)       | event `LB WAF Activity` (source `ews.waf`), with the top rules and clients                      |
| Web ACL counts per minute                                       | metrics `waf_blocked`, `waf_counted`, `waf_challenged`, `waf_rate_limited` of the load balancer |
| A provider type sold out at creation                            | an Insufficient Capacity event; the load balancer goes to `error`                               |

See [Events](/docs/events).

## Status values

| Load balancer `status` | Meaning                                                                         |
| ---------------------- | ------------------------------------------------------------------------------- |
| `provisioning`         | Being created or placed; no address yet.                                        |
| `active`               | Placed. What it serves depends on its services and targets.                     |
| `deleting`             | Being removed.                                                                  |
| `error`                | Creation or deletion failed; the reason is on its page and in `reconcileError`. |

A target's `status` is `healthy`, `unhealthy` or `unknown`; on `lb11`–`lb31` it is not updated
from the health check. See [Health checks](health-checks.md).

## Related

- [Health checks](health-checks.md)
- [Troubleshooting](troubleshooting.md)
