# loglevel

While executing a USE script, various messages are written to a logfile. The `loglevel` option determines the amount of detail recorded in that logfile.

## Syntax

**`loglevel`***`loglevel`*

## Details

The table below shows the valid values for the *loglevel* argument. Either the numeric level or the label can be specified. If the label is used then it must be specified in CAPITAL LETTERS.

The log levels are cumulative, in that higher log-level values include lower level messages. For example a level of `INFO` will cause `FATAL`, `ERROR`, `WARN` and `INFO` level messages to be written to the log.

| Level | Label    | Meaning                         |
| ----- | -------- | ------------------------------- |
| `0`   | `DEBUGX` | Extended debugging information  |
| `1`   | `DEBUG`  | Debugging information           |
| `2`   | `INFO`   | Standard informational messages |
| `3`   | `WARN`   | Warnings and non-fatal errors   |
| `4`   | `ERROR`  | Run-time errors                 |
| `5`   | `FATAL`  | Non-recoverable errors          |

The `loglevel` statement takes immediate effect and may be used multiple times within a USE script in order to increase or decrease the logging level at any time.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://olddocs.exivity.io/2.10.2/data-pipelines/extract/language/loglevel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.