Types of Logging
Understand the different types of logging that PingAccess offers.
PingAccess logging is handled by a high performance, asynchronous logging framework. Learn more in Logging. PingAccess provides the following additional types of logging:
- Audit logging
-
Logs a select subset of transaction log information at runtime plus additional details meant to facilitate security auditing and regulatory compliance. If you don’t require auditing for interactions with a resource or interactions between PingAccess and PingFederate, it’s most efficient to disable audit logging.
If you use audit logging, you should take appropriate steps to secure your audit log files. You can find more information about security measures or audit logging in Security audit logging.
- HAR file audit logging
-
Logs detailed records of specific transactions and sub-transactions between PingAccess and other systems, such as the configured OAuth authorization server (OAuth AS) or a system acting on behalf of the end user.
HAR-formatted audit log files are significantly larger than other log files and can include credentials. You should either carefully configure regex filters to exclude credential information or enable these logs only for troubleshooting purposes. Delete the files when they are no longer necessary.
You can find more information about HAR file audit logging and regex filters in Log traffic for troubleshooting.
- Garbage collection logging
-
Logs details related to each occurrence of Java garbage collection.
PingAccess logs Java garbage collection data by default, but you can configure garbage collection properties or disable this type of logging. Learn more in Garbage collection logging.
- Agent inventory logging
-
Logs details about your PingAccess agents. Adding the optional header
vnd-pi-agentto an agent allows it to communicate information about itself and its deployment environment to PingAccess.Learn more in Agent inventory logging.
- Cookie logging
-
Logs information about the PingAccess cookie, which contains all request identity mappings and the access token from PingFederate, if PingFederate is the AS.
Cookie logging is an optional feature in the
TRACElog level. It isn’t enabled by default. Learn more in Enabling cookie logging.
|
You can also configure PingAccess to write log files in Common Event Format (CEF), or to write log files to Splunk or a database. Learn more in Other logging formats. |