Enabling debug logging
To help with troubleshooting or monitoring, you can turn on activity logging for PingFederate, the Island Enterprise Browser Device Trust IdP Adapter, or both. You can also use logging for analytics.
This task is optional. |
You can find general information about logging in Enabling debug messages and console logging in the PingFederate documentation.
Steps
-
Open the
<pf_install>/pingfederate/server/default/conf/log4j2.xml
file for editing. -
To log activity for PingFederate and all adapters:
-
Go to the following section in the
log4j2.xml
file:<AsyncRoot level="INFO" includeLocation="false"> <!-- <AppenderRef ref="CONSOLE" /> --> <AppenderRef ref="FILE" /> </AsyncRoot>
-
Change
INFO
toDEBUG
:<AsyncRoot level="DEBUG" includeLocation="false"> <!-- <AppenderRef ref="CONSOLE" /> --> <AppenderRef ref="FILE" /> </AsyncRoot>
-
(Optional) To see the adapter activity in the console as well as the log file, remove the comment tags surrounding the CONSOLE line:
<AsyncRoot level="INFO" includeLocation="false"> <AppenderRef ref="CONSOLE" /> <AppenderRef ref="FILE" /> </AsyncRoot>
-
-
To log only activity relating to the Island Enterprise Browser Device Trust IdP Adapter, do one of the following:
Choose from:
-
To log activity for the Island Enterprise Browser Device Trust IdP Adapter as well as its HTTPS and component activity, add the following line:
<Logger name ="com.pingidentity.adapters.island.device.trust" level="DEBUG"/>
-
To log activity for the adapter’s HTTPS activity and other components, but not the adapter itself, add the following line:
<Logger name ="com.pingidentity.adapters.island.device.trust.shade" level="DEBUG"/>
-
To log activity for the Island Enterprise Browser Device Trust IdP Adapter but not its HTTPS or component activity, add the following lines:
<Logger name ="com.pingidentity.adapters.island.device.trust" level="DEBUG"/> <Logger name ="com.pingidentity.adapters.island.device.trust.shade" level="INFO"/>
-
-
Save the file.