The debug level, by default, is set to error. The debug files might be useful to an administrator when they are:
Writing a custom authentication module.
Writing a custom application using the Access manager SDKs. The amProfile and amSDK debug files capture this information.
Troubleshooting access permissions while using the console or SDK. The amProfile and amSDK debug files also capture this information.
Troubleshooting SSL.
Troubleshooting the LDAP authentication module. The amAuthLDAP debug file captures this information.
The debug files should go hand in hand with any troubleshooting guide we might have in the future. For example when SSL fails, someone might turn on debug to message and look in the amJSS debug file for any specific certificate errors.