# `LogLevel`

How severe a log record is (OpenTelemetry's severities), written as its short name, `INFO`.

[Software](types.md#software); not ordered; since Jadpo 0.1.0.

## Make one

Pick one of its variants, `LogLevel.trace`.

`text.parse(raw, as: LogLevel)` reads one from its text; text that isn't one at all fails `malformed`, such as `WARNING`, `CRITICAL` or `INFO `.

## Variants

| Variant | Written |
|---|---|
| `trace` | `TRACE` |
| `debug` | `DEBUG` |
| `info` | `INFO` |
| `warn` | `WARN` |
| `error` | `ERROR` |
| `fatal` | `FATAL` |

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `TRACE` | `"TRACE"` |
| `INFO` | `"INFO"` |
| `FATAL` | `"FATAL"` |

It is stored in one column named for the field, of type `text`. `INFO` is stored as `'INFO'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `TRACE` | `TRACE` |
| `INFO` | `INFO` |
| `FATAL` | `FATAL` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.