Creating File-Based Debug Log Publishers

PingAuthorize Server provides a File-Based Debug Log Publisher that can be configured when troubleshooting a problem that could occur during server processing.

Because the debug data might be too large to maintain during normal operations, the Debug Log Publisher must be specifically configured and enabled. The Debug Log reports the following types of information:

Exception data thrown by the server.
Data read or written to network clients.
Data read or written to the database.
Access control or password policy data made within the server.

Use the dsconfig tool to create a debug log publisher.

You should only create a debug logger when troubleshooting a problem because of the voluminous output PingAuthorize Server generates.

Creating a File-Based Debug Log Publisher

Steps

To create the debug log publisher, use dsconfig.

The log-file property (required) sets the debug log path. You must also specify the rotation and retention policy for the debug log.

Example:

$ bin/dsconfig create-log-publisher \
  --publisher-name "File-Based Debug Logger" \
  --type file-based-debug \
  --set enabled:true \
  --set log-file:/logs/debug \
  --set "rotation-policy:24 Hours Time Limit Rotation Policy" \
  --set "rotation-policy:Size Limit Rotation Policy" \
  --set "retention-policy:File Count Retention Policy"

Deleting a File-Based Debug Log Publisher

Steps

To create the debug log publisher, use dsconfig.

Example:

$ bin/dsconfig delete-log-publisher \
  --publisher-name "File-Based Debug Logger"