# log, levels

> How to set the log level in evcc.yaml, what the levels from fatal to trace mean and how to raise the level for single components such as a charging point.

## `log`

Defines the level of detail for logging information to the console.

**Possible values**:

* `fatal`: Only messages of the `fatal` category will be displayed. These are errors that prevent the system from functioning.
* `error`: Only messages of the `error` category will be displayed. There are very few of this type of message.
* `warn`: Includes `error`, additionally shows messages of the `warn` category.
* `info`: Includes `warn`, additionally shows messages of the `info` category.
* `debug`: Includes `info`, additionally shows messages of the `debug` category. This is necessary for error analysis.
* `trace`: Includes `debug`, additionally shows messages of the `trace` category. This is the most detailed category and can result in very large log data. In general, this is not usually needed!

The setting applies to the [long-term logs](/en/report-a-problem#system-logs) of your installation. The Logs page in the web interface always records all levels, see [Logs](/en/report-a-problem#logs).

**For example**:

```yaml
log: error
```

***

## `levels`

Allows configuring different logging levels for various components of evcc.

Defines the level of detail for logging for different evcc components.

**Possible components**:

* `site`: The central evcc component (control, calculations, …)
* `lp-X`: The respective charging point, where `X` is numbered according to the order of [`loadpoints`](/en/reference/configuration/loadpoints) configuration (charging points), starting at `1`
* `sma`: The SMA HEMS component if SMA Sunny Home Manager 2.0 is integrated using [`hems`](/en/reference/configuration/hems)
* *`vehicle`*: Each [`vehicle`](/en/reference/configuration/vehicles) (vehicle), where you must specify the corresponding value of the [`type`](/en/reference/configuration/vehicles#type) parameter (or template).
* Additionally, depending on the use case, additional components can be specified (e.g. `cache`, `db`, `influx`, `mqtt`, …)

**Possible values for each component**: Identical to the values of [`log`](#log)

**For example**:

```yaml
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  tesla: trace
```