> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/password-reset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/password-reset/operations/troubleshooting/extended-logging.md).

# Extended logging

Extend logging for Password Reset components when additional troubleshooting detail is needed.

All changes should be made in `log4j2.xml`, located in `<installation path>\pwdreset\config`, where the installation path depends on the operating system and installation setup.

## Specific logging for Password Reset components

Locate the `AsyncLoggers` section in `log4j2.xml` and add:

```xml
<AsyncLogger name="fortified.pwdreset" level="DEBUG" />
```

Use `TRACE` instead of `DEBUG` if you need even more detailed logging.

## Generic logging for Fortified ID components

You can also increase logging more broadly for Fortified ID components:

```xml
<AsyncLogger name="fortifiedid" level="INFO" />
<AsyncLogger name="fortified" level="INFO" />
<AsyncLogger name="foss" level="INFO" />
```

Change `INFO` to `DEBUG` or `TRACE` when more detailed troubleshooting information is needed.

Examples of when extended logging can be useful:

* troubleshooting failed password reset flows
* understanding how the PasswordReset module behaves during a request
* collecting additional detail when support or development needs more context

Additional log settings and information are available here: [Log settings](https://docs.fortifiedid.se/log-settings)