Relog
Updated: January 21, 2005
Syntax
Parameters
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:
- \\computer\object(parent/instance#index)\counter
- \\computer\object(parent/instance)\counter
- \\computer\object(instance#index)\counter
- \\computer\object(instance)\counter
- \\compyuter\object\counter
- \object(parent/instance#index)\counter
- \object(parent/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 (that is, -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 -e (that is, end time) parameter.
-
Using the -config option
The contents of the setting file used with the -config option should have the following format:
[CommandOption]
Value
where CommandOption 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 WMI" at the Microsoft Windows Resource Kits Web site .
Examples
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:
Relog c:\perflogs\daily_trace_log.blg -cf counter_file.txt -o c:\perflogs\reduced_log.blg -t 30
Formatting legend
Format | Meaning |
Italic | Information that the user must supply |
Bold | Elements that the user must type exactly as shown |
Ellipsis (...) | Parameter that can be repeated several times in a command line |
Between brackets ([]) | Optional items |
Between braces ({}); choices separated by pipe (|). Example: {even|odd} | Set of choices from which the user must choose only one |
Courier font | Code or program output |