> For the complete documentation index, see [llms.txt](https://docs.inrupt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inrupt.com/ess/2.4/installation/customize-configurations/customization-logging/modify-log-level.md).

# Update Log Level

ESS services support a subset of log levels supported by Quarkus:

* **`FATAL`**
* **`ERROR`**
* **`WARN`**
* **`INFO`** (Default level)
* **`DEBUG`**

By default, ESS’ log level is configured to **`INFO`** level:

* This outputs logs with severity level **`INFO`** and higher (i.e., outputs **`INFO`** , **`WARN`** , **`ERROR`** and **`FATAL`** levels).
* This excludes logs with security level below **`INFO`** (i.e., excludes **`DEBUG`** ).

As part of your infrastructure-as-code deployment, you may wish to control log levels of the deployments using a customization.

For example, when debugging an issue you may temporarily enable **`DEBUG`** level logs to get more granular information on system behavior.

To change a service’s log level, you can create an overlay to update the **`QUARKUS_LOG_LEVEL`** environment variable.

{% hint style="info" %}
ESS also supports changing the level of log messages using redaction. See [Logging Redaction](/ess/2.4/administration/logging/logging-redaction.md) for details.
{% endhint %}

## Example Debug Logging Customization File

You can use the following procedure to enable **`DEBUG`** level logging for **`pod-provisioning`** :

1. Go to your ESS installation directory:

   ```sh
   cd ${HOME}/ess
   ```
2. Modify the **`kustomization.yaml`** (i.e., step 3 of the [Applying Your Customizations](/ess/2.4/installation/customize-configurations.md#applying-your-customizations) procedure).\
   Specifically, add the highlighted content to the **`kustomization.yaml`** file under the **`patches`** key:

{% hint style="info" %}
**Tip** If **`patches`** list does not exist in **`kustomization.yaml`** , add the key **`patches`** as well.
{% endhint %}

```yaml
# kustomization.yaml in your ESS installation directory
# ...  Preceding content omitted for brevity 
# ...
patches:
  - target:
      kind: Deployment
      name: ess-pod-provision
    patch: |-
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: ess-pod-provision
      spec:
        template:
          spec:
            containers:
              - env:
                - name: QUARKUS_LOG_LEVEL
                  value: DEBUG
                name: ess-pod-provision
```

3. Continue with the rest of the [Applying Your Customizations](/ess/2.4/installation/customize-configurations.md#applying-your-customizations) procedure.

{% hint style="info" %}
**Tip**\
Remember to reset the log level when you’re finished debugging.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.inrupt.com/ess/2.4/installation/customize-configurations/customization-logging/modify-log-level.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.