p4 logparse

Synopsis

Parse a structured log file and return log data.

Syntax

p4 [g-opts] logparse [-e] [-T fields...] [-F filter] [-s offset] [-m max] logfile

Description

The p4 logparse command parses the indicated structured logfile and returns the log data in tagged format.

Structured logs differ from the basic error log (P4LOG) and audit log (P4AUDIT). To read the basic error log, use the p4 logtail command.

Valid names for structured log files are shown in the table below:

all.csv

All loggable events (commands, errors, audit, etc.)

audit.csv

Audit events (audit, purge)

auth.csv

Information about user login attempts.

commands.csv

Command events (command start, command compute, command end)

errors.csv

Error events (errors-failed, errors-fatal)

track.csv

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

user.csv

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

events.csv

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

integrity.csv

Major events that occur during replica integrity checking.

To enable structured logging, set the serverlog.file.n configurable(s) to the name of the file. For example: 

$ p4 configure set serverlog.file.2=commands.csv
$ p4 configure set serverlog.file.3=errors.csv
$ p4 configure set serverlog.file.5=audit.csv

Numbers provided for the configurables do not have to be consecutive. A given number may not exceed 500; this assignment will return an error: 

$ p4 configure set serverlog.file.666=commands.csv

Structured log files are automatically rotated on checkpoint, journal creation, overflow of associated serverlog.maxmb.n limit (if configured), and the p4 logrotate command.

Options

-e

Display special characters as hex-encodings.

-F filter

Limit output to records that match the filter pattern.

-m max

Limit the number of lines returned.

-s f_offset

Start parsing at the given file offset as returned in the f_offset field.

-T fields...

Limit displayed fields to those listed.

g-opts

See “Global Options”.

Usage Notes

Can File Arguments Use Revision Specifier? Can File Arguments Use Revision Range? Minimal Access Level Required

N/A

N/A

super