Helix Core Server Administrator Guide: Fundamentals (2019.1)

Enabling structured logging

To enable structured logging, set the serverlog.file.N configurable to the name of the file.

Valid names for structured log files and the information logged are shown in the following table. You can use a file path in conjunction with the file name.

Warning

You must use one of the file names specified in the table. If you use an arbitrary name, no data will be logged to the file you specify.

Filename Description

all.csv

All loggable events (commands, errors, audit, triggers, and more)

audit.csv

Audit events (audit, purge)

auth.csv

The results of p4 login attempts. If the login failed, the reason for this is included in the log. Additional information provided by the authentication method is also included.

commands.csv

Command events (command start, compute, and end)

errors.csv

Error events (errors-failed, errors-fatal)

events.csv

Server events (startup, shutdown, checkpoint, journal rotation, etc.)

integrity.csv

Major events that occur during replica integrity checking.

ldapsync.csv

p4 ldapsync events, such as when:

  • a user is added, updated, or removed
  • a user is added or removed from a group

route.csv

Log the full network route of authenticated client connections. Errors related to net.mimcheck are also logged against the related hop.

track.csv

Command tracking (track-usage, track-rpc, track-db)

triggers.csv

Trigger events.

user.csv

User events; one record every time a user runs p4 logappend.

Files do not have to be set in consecutive order:

$ p4 configure set serverlog.file.1=audit.csv
$ p4 configure set serverlog.file.2=auth.csv
$ p4 configure set serverlog.file.4=track.csv
$ p4 configure set serverlog.file.3=triggers.csv
Note

Enabling all structured logging files can consume considerable diskspace. See Structured logfile rotation for information on how to manage the size of the log file and the number of log rotations.

The value you specify for N may not exceed 500.