CPLogInvestigator

Description

This heuristic tool can analyze the specified logs files from managed Security Gateways and show:

  • The estimated number of events per day.

  • The number of logs from each Software Blade.

  • The number of logs during each minute.

Important - You can run this command only in the Expert mode.

Syntax

CPLogInvestigator

      [-h]

      [-d]

      [-a]

      [{-i /<Path>/<Name of Log File> | -f <Path to Directory>}]

      [-l]

      [-m]

      [-p]

      [-u <Number of Users>]

Parameters

Parameter

Description

-h

Shows the built-in help.

No Parameters

Analyzes the events in all the $FWDIR/log/*.log files (the active log and the rotated logs).

The default analysis duration for each log file is 60 seconds.

-d

Runs the command in debug mode.

Use only if you troubleshoot the command itself.

Best Practice - If you use this parameter, then redirect the output to a file, or use the script command to save the entire CLI session.

This option "-d" is not supported (ignored) when specified together with the option "-p".

-a

Analyzes the events in all the "*.log" files - the active log and the rotated logs.

The default path is $FWDIR/log/.

The default analysis duration is 60 seconds.

If the number of log files is large, and the log files are large, then the analysis can take significant time.

-f <Path to Directory>

Analyzes the events in all the "*.log" files in the specified directory.

This parameter must the last parameter in the syntax.

-i /<Path>/<Name of Log File>

Analyzes the events in the specified log file.

This parameter must the last parameter in the syntax.

-l

Limits the duration of the analysis to 60 seconds.

-m

Saves the number of logs for each minute of analyzes log files in the output file called "logPerMinute.txt" in the current working directory.

-p

Shows the daily estimated number of logs from each Software Blade that generated these logs.

-u <Number of Users>

Specifies the number of required users to show estimations for events from the Application Control and the URL Filtering Software Blades.

Examples