Federation Services logging is set in the following file:
[Federation Services folder]/WEB-INF/classes/log4j.properties
You can set the log level of all Federation Services classes by changing the following:
log4j.logger.com.simflofy = debug, 3sixty-admin
Replace debug with another valid options:
| Level | Description |
|---|---|
| ALL | All levels including custom levels. |
| DEBUG | Designates fine-grained informational events that are most useful to debug an application. |
| ERROR | Designates error events that might still allow the application to continue running. |
| FATAL | Designates very severe error events that will presumably lead the application to abort. |
| INFO | Designates informational messages that highlight the progress of the application at coarse-grained level. |
| OFF | The highest possible rank and is intended to turn off logging. |
| TRACE | Designates finer-grained informational events than the DEBUG. |
| WARN | Designates potentially harmful situations. |
In production, Federation Services suggests setting logging to the ERROR level.
You’ll notice there are other entries. These entries will override the com.simflofy setting for the specific packages they reference.
For example, this sets the SharePoint connector logging to TRACE. The second line is necessary to prevent double-logging:
log4j.logger.com.simflofy.connectors.sharepoint = trace, 3sixty-admin log4j.additivity.com.simflofy.connectors.sharepoint = false