> For the complete documentation index, see [llms.txt](https://ajuda.rnp.br/cafe/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajuda.rnp.br/cafe/idp-cafe/faq/untitled-3.md).

# Altera nível do log do IDP para DEBUG

Esse procedimento visa alterar o nível do log do IdP para o modo DEBUG, com isso mais informações serão gravadas e informadas para uma melhor analise do problema.

### Guia passo a passo

Altere o nível do log para **DEBUG**. Abra o arquivo  **/opt/shibboleth-idp/conf/logback.xml**  e altere as linhas **24,25 e 28** abaixo:

<pre class="language-sh" data-line-numbers><code class="lang-sh">&#x3C;?xml version="1.0" encoding="UTF-8"?>
&#x3C;configuration>

    &#x3C;!--
    Variables for simplifying logging configuration.
    http://logback.qos.ch/manual/configuration.html#variableSubstitution
    -->

    &#x3C;!--
    If you want to use custom properties in this config file,
    we load the main property file for you.
    -->
    &#x3C;variable file="${idp.home}/conf/idp.properties" />

    &#x3C;!-- Location and retention. -->

    &#x3C;variable name="idp.logfiles" value="${idp.logfiles:-${idp.home}/logs}" />
    &#x3C;variable name="idp.loghistory" value="${idp.loghistory:-180}" />

    &#x3C;!-- Much higher performance if you operate on DEBUG. -->
    &#x3C;!-- &#x3C;variable name="idp.process.appender" value="ASYNC_PROCESS" /> -->

    &#x3C;!-- Logging level shortcuts. -->
<strong>    &#x3C;variable name="idp.loglevel.idp" value="${idp.loglevel.idp:-INFO}" />
</strong><strong>    &#x3C;variable name="idp.loglevel.ldap" value="${idp.loglevel.ldap:-WARN}" />
</strong>    &#x3C;variable name="idp.loglevel.messages" value="${idp.loglevel.messages:-INFO}" />
    &#x3C;variable name="idp.loglevel.encryption" value="${idp.loglevel.encryption:-INFO}" />
<strong>    &#x3C;variable name="idp.loglevel.opensaml" value="${idp.loglevel.opensaml:-INFO}" />
</strong>    &#x3C;variable name="idp.loglevel.props" value="${idp.loglevel.props:-INFO}" />
    &#x3C;variable name="idp.loglevel.httpclient" value="${idp.loglevel.httpclient:-INFO}" />

    &#x3C;!-- Don't turn these up unless you want a *lot* of noise. -->
    &#x3C;variable name="idp.loglevel.spring" value="${idp.loglevel.spring:-ERROR}" />
    &#x3C;variable name="idp.loglevel.container" value="${idp.loglevel.container:-ERROR}" />
    &#x3C;variable name="idp.loglevel.xmlsec" value="${idp.loglevel.xmlsec:-INFO}" />

    &#x3C;!-- =========================================================== -->
    &#x3C;!-- ============== Logging Categories and Levels ============== -->
    &#x3C;!-- =========================================================== -->
...
...
...
</code></pre>

#### Nas linhas citadas acima alterar para que fiquem como o exemplo abaixo:

<pre class="language-sh"><code class="lang-sh"><strong>&#x3C;variable name="idp.loglevel.idp" value="${idp.loglevel.idp:-DEBUG}" />
</strong><strong>&#x3C;variable name="idp.loglevel.ldap" value="${idp.loglevel.ldap:-DEBUG}" />
</strong>&#x3C;variable name="idp.loglevel.messages" value="${idp.loglevel.messages:-INFO}" />
&#x3C;variable name="idp.loglevel.encryption" value="${idp.loglevel.encryption:-INFO}" />
<strong>&#x3C;variable name="idp.loglevel.opensaml" value="${idp.loglevel.opensaml:-DEBUG}" />
</strong></code></pre>

####

#### Faça o restart do serviço com o comando abaixo:

```shellscript
sudo systemctl restart jetty.service
```

#### Aguarde o serviço voltar e pronto, seu log está em modo DEBUG para o IdP.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ajuda.rnp.br/cafe/idp-cafe/faq/untitled-3.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.