Enabling debug logging

To help with troubleshooting or monitoring, you can turn on activity logging for the adapter.

About this task

These steps are optional.

For general information about logging, see Enabling debug messages and console logging in the PingFederate documentation.

Open the <pf_install>/pingfederate/server/default/conf/log4j2.xml file for editing.

If you want to log activity for PingFederate and all adapters, do the following.

Find the following section.

<AsyncRoot level="INFO" includeLocation="false">
	<!-- <AppenderRef ref="CONSOLE" /> -->
	<AppenderRef ref="FILE" />
</AsyncRoot>

Change INFO to DEBUG.

<AsyncRoot level="DEBUG" includeLocation="false">
	<!-- <AppenderRef ref="CONSOLE" /> -->
	<AppenderRef ref="FILE" />
</AsyncRoot>

If you want to see the adapter activity in the console, remove the comment tags.

<AsyncRoot level="INFO" includeLocation="false">
	<AppenderRef ref="CONSOLE" />
	<AppenderRef ref="FILE" />
</AsyncRoot>

If you want to log activity just for the ID DataWeb IdP Adapter, add the following line.
```
<Logger name="com.pingidentity.adapters.id-dataweb" level="DEBUG"/>
```
If you want to log all HTTP requests and responses with the ID DataWeb API, add the following line.

You can use this information with a third-party log analysis tool to monitor for important events, such as when a sign-on event has a high-risk policy decision.
```
<Logger name="org.shaded.{file-prefix}" level="INFO"/>
```
Save the file.