Enabling engine traffic logging
Enable engine audit logging, including requests and responses.
Steps
- 
Edit the <PA_HOME>/conf/log4j2.xmlfile.
- 
In the Logger section, uncomment the AppenderRefelement for the engine audit log HAR file.Example:<!-- Audit Log Configuration--> ... <Logger name="engineaudit" level="INFO" additivity="false"> <AppenderRef ref="EngineAuditLog-File"/> <!--<AppenderRef ref="EngineAuditLog-Database-Failover"/>--> <!--<AppenderRef ref="EngineAuditLog-SQLServer-Database-Failover"/>--> <!--<AppenderRef ref="EngineAuditLog-PostgreSQL"/>--> <!--<AppenderRef ref="EngineAudit2Splunk"/>--> <AppenderRef ref="EngineAuditLog-HarFile"/> </Logger>
- 
In the Appenders section, uncomment the RollingFileelement for the engine audit log HAR file.Example:<Appenders> ... <RollingFile name="EngineAuditLog-HarFile" fileName="${sys:pa.home}/log/pingaccess_engine_audit_har.log" filePattern="${sys:pa.home}/log/pingaccess_engine_audit_har.%d{yyyy-MM-dd}.log" ignoreExceptions="false"> <StatusCodeRegExFilter regex=".*"/> <HarLogLayout> <KeyValuePair key="AUDIT.metadata" value="true"/> <KeyValuePair key="AUDIT.http-client" value="true"/> <KeyValuePair key="AUDIT.http-app" value="true"/> </HarLogLayout> <Policies> <TimeBasedTriggeringPolicy /> </Policies> </RollingFile>
- 
Optional: To filter the entries to add to the log file, edit the value of the StatusCodeRegExFilterelement.
- 
Optional: To specify what information to log, add or edit the values in the HarLogLayoutsection of theRollingFileelement.You can add or edit metadata, client response, and app response values. For more information, see Traffic logging reference. 
Result
Logging begins when the configuration reloads. The configuration reloads at regular intervals according to the monitorInterval value.