P4AUDIT

Location of the audit log file.

Usage Notes

Used by Client?	Used by Server?	Command-Line Alternative	Can be set in P4CONFIG file?
No	Yes	`p4d -A auditlog`	N/A

Value if not Explicitly Set

Operating System	Value
All	None. If no log file is specified, auditing is disabled.

Notes

P4AUDIT specifies the location of the audit log file.

When auditing is enabled, Helix Server adds a line to the audit log file every time file content is transferred to any user. To ensure that user activity on forwarding replicas, edge servers, and build farm replicas is tracked, each replica or edge server must have P4AUDIT configured.

Important

On any active server, the audit log file grows quickly. Make a plan to manage the disk space. Include in your plan any retention policies for storing historical copies of the audit log files.

Lines in the audit log appear in the form:

datetimeuser@clientclientIPcommandfile#rev

For example:

2011/05/09 09:52:45 karl@nail 192.168.0.12 diff //depot/src/x.c#1
2011/05/09 09:54:13 jim@stone 127.0.0.1 sync //depot/inc/file.h#1

If a command is run on the same physical machine that hosts the Perforce service, the clientIP is shown as 127.0.0.1.

For commands that arrive through a Helix Proxy, the IP address is reported in the form proxyIP/clientIP, and the command is reported as command-proxy.

See Auditing user file access in the Helix Core Server Administrator Guide.