Relog

Extracts performance counters from performance counter logs into other formats, such as text-TSV (for tab-delimited text), text-CSV (for comma-delimited text), binary-BIN, or SQL.

Syntax

relog [FileName [filename ...]] [-a] [-c Path [path ...]] [-cf FileName] [-f {bin|csv|tsv|SQL}] [-t value] [-o {output file | DSN!counter_log}] [-b M/d/yyyy [[hh:]mm:]ss] [-e M/d/yyyy [[hh:]mm:]ss] [-config FileName] [-q]

Parameters

FileName [ filename ... ] : Specifies the pathname of an existing performance counter log. You can specify multiple input files.

-a   : Appends output file instead of overwriting. This option does not apply to SQL format where the default is always to append.

-c   Path [ path ... ] : Specifies the performance counter path to log. To specify multiple counter paths, separate them with a space and enclose the counter paths in quotation marks (for example, "CounterPath1 CounterPath2").

-cf   FileName   : Specifies the pathname of the text file that lists the performance counters to be included in a relog file. Use this option to list counter paths in an input file, one per line. Default setting is all counters in the original log file are relogged.

-f { bin | csv | tsv | SQL } : Specifies the pathname of the output file format. The default format is bin. For a SQL database, the output file specifies the DSN!counter_log. You can specify the database location by using the ODBC manager to configure the DSN (Database System Name).

-t   value   : Specifies sample intervals in "n" records. Includes every nth data point in the relog file. Default is every data point.

-o { output file | DSN!counter_log } : Specifies the pathname of the output file or SQL database where the counters will be written.

-b   M/d/yyyy   hh[:mm[:ss]]   : Specifies begin time for copying first record from the input file. Date and time must be in this exact format M/d/yyyy hh:mm:ss.

-e   M/d/yyyy   hh[:mm[:ss]]   : Specifies end time for copying last record from the input file. Date and time must be in this exact format M/d/yyyy hh:mm:ss.

-config   FileName   : Specifies the pathname of the settings file that contains command-line parameters.

-q   : Displays the performance counters and time ranges of log files specified in the input file.

/?   : Displays help at the command prompt.

Remarks

• Counter path format

  The general format for counter paths is as follows: [\\Computer]\object[parent/instance#index]\counter] where:

  The parent, instance, index, and counter components of the format may contain either a valid name or a wildcard character. The computer, parent, instance, and index components are not necessary for all counters.

  You determine the counter paths to use based on the counter itself. For example, the LogicalDisk object has an instance index, so you must provide the #index or a wildcard. Therefore, you could use the following format:

  \LogicalDisk(*/*#*)\*

  In comparison, the Process object does not require an instance index. Therefore, you could use the following format:

  \Process(*)\ID Process

  The following is a list of the possible formats:

  • \\machine\object(parent/instance#index)\counter

  • \\machine\object(parent/instance)\counter

  • \\machine\object(instance#index)\counter

  • \\machine\object(instance)\counter

  • \\machine\object\counter

  • \object(parent/instance#index)\counter

  • \object(parent/instance)\counter

  • \object(instance#index)\counter

  • \object(instance)\counter

  • \object\counter

  If a wildcard character is specified in the parent name, all instances of the specified object that match the specified instance and counter fields will be returned.

  If a wildcard character is specified in the instance name, all instances of the specified object and parent object will be returned if all instance names corresponding to the specified index match the wildcard character.

  If a wildcard character is specified in the counter name, all counters of the specified object are returned.

  Partial counter path string matches (for example, pro*) are not supported.

• Counter files

  Counter files are text files that list one or more of the performance counters in the existing log. Copy the full counter name from the log or the -q output in [\\Computer \ object [instance] \ counter] format. List one counter path on each line.

• Copying counters

  When executed, Relog copies specified counters from every record in the input file, converting the format if necessary. Wildcard paths are allowed in the counter file.

• Saving input file subsets

  Use the -t parameter to specify that input files are inserted into output files at intervals of every nth record. By default, data is relogged from every record.

• Using -b and -e parameters with log files

  You can specify that your output logs include records from before begin-time (-b) to provide data for counters that require computation values of the formatted value. The output file will have the last records from input files with timestamps less than the end-time (-e) parameter.

• Using the -config option

  The contents of the setting file used with the -config option should have the following format:

  [command_option]

  value

  where command_option is a command line option and value specifies its value. For example:

  [o]

  output.txt

  [f]

  csv

  [t]

  5

• For more information about incorporating Relog into your Windows Management Instrumentation (WMI) scripts, see Scripting Logs and Monitoring at the Microsoft Windows Resource Kits Web site.

Examples

To resample existing trace logs at fixed intervals of 30, list counter paths, output files and formats, type the following command:

Relog c:\perflogs\daily_trace_log.blg -cf counter_file.txt -o c:\perflogs\reduced_log.csv -t 30 -f csv

To resample existing trace logs at fixed intervals of 30, list counter paths and output files, type the following command:

Relog c:\perflogs\daily_trace_log.blg -cf counter_file.txt -o c:\perflogs\reduced_log.blg -t 30

Formatting legend

Logman

Tracerpt

Typeperf

Command-line reference A-Z