relog: Relog creates new performance logs from data in existing performance logs by changing the sampling rate and/or converting the fi ...
The command: "relog" is on Windows 11, 10, .. available
"relog" Excerpt from Microsoft Windows Help
Microsoft Windows [Version 10.0.19045.3693]
(c) Copyright 1985-2023 Microsoft Corp.
C:\\WINDOWS>
Microsoft r Relog.exe (5.1.2600.0)
c Microsoft Corporation. All rights reserved.
Relog creates new performance logs from data in existing performance logs by
changing the sampling rate and/or converting the file format. Supports all
performance log formats, including Windows NT 4.0 compressed logs.
Usage:
relog <filename [filename ...]>
[options]
Parameters:
<filename [filename ...]> Performance file to relog.
Options:
-? Displays context sensitive help.
-a Append output to existing binary file.
-c <path [path ...]> Counters to filter from input log.
-cf <filename> File listing performance counters to filter
form the input log. Default is all counters
in the original log file.
-f <CSV|TSV|BIN|SQL> Output file format.
-t <value> Only write every nth record into the output
file. Default is to write every record.
-o Output file path or SQL database.
-b <M/d/yyyy h:mm:ss[AM|PM]> Begin time for the first record to write into
the output file.
-e <M/d/yyyy h:mm:ss[AM|PM]> End time for the last record to write into
the output file.
-config <filename> Settings file containing command options.
-q List performance counters in the input file.
-y Answer yes to all questions without
prompting.
Examples:
relog logfile.csv -c "\Processor(_Total)\% Processor Time" -o logfile.blg
relog logfile.blg -cf counters.txt -f blg
relog logfile.blg -f csv -o logfile.csv -t 2
relog logfile.blg -q -o counters.txt
The examples for the command "relog"
The
`relog` command is used in the Windows Command Prompt to write or display performance data to a log file. Here are some examples of using
`relog`:
Example 1: Export performance data to a CSV file:
relog PerfMonLog.blg -f CSV -o ExportedData.csv
- Exports the performance data from the log file
"PerfMonLog.blg" to CSV format and saves it to the file
"ExportedData.csv".
Example 2: View performance data in Command Prompt:
relog PerfMonLog.blg -o -
- Displays the performance data from the log file
"PerfMonLog.blg" directly in the command prompt. The
`-o -` causes the data to be displayed on standard output.
Example 3: Filtering performance data by a specific time period:
relog PerfMonLog.blg -b "11/01/2023 00:00:00" -e "11/02/2023 23:59:59" -o FilteredData.blg
- Exports the performance data from the log file
"PerfMonLog.blg", which was collected only from November 1, 2023, 00:00 to November 2, 2023, 23:59, and saves it in the file
"FilteredData. blg".
Example 4: Converting performance data to SQL database format:
relog PerfMonLog.blg -f SQL -o PerfMonDatabase.sql
- Converts the performance data from the PerfMonLog.blg log file to SQL format and saves it to the PerfMonDatabase.sql file.
These examples should give you an idea of ??how the
`relog` command can be used in different scenarios. Note that actual options and parameters may vary depending on available performance data and desired output format.
Important information, tips for the "relog" command
When using the `relog` command, there are a few important points to pay attention to:
1. Note file format: Make sure you select the correct file format for your needs. Supported formats include binary (BLG), CSV, SQL and more. Use the `-f` or `-f:Format` option as appropriate.
2. Filenames and Paths: Be sure to provide valid filenames and paths for your log files. Avoid special characters or spaces, which can cause problems. Use quotation marks if the path contains spaces.
3. Time filtering: If you use a time filter (`-b` and `-e`), ensure that you are using the correct date and time format and that the times specified are within the range of existing performance data.
4. Compatibility: Make sure the version of `relog` on your system is compatible with the performance data collected. Sometimes different versions may support different features and options.
5. Data Consistency: When exporting performance data or converting it to another format, check the consistency of the data to ensure that no information has been lost and that the converted data can be interpreted correctly.
6. Storage Space: Check the available space on the drive where you want to save the export files. Performance data can be significant and sufficient storage capacity is important.
7. Permissions: Make sure you have sufficient permissions to access the performance data and the destination folder.
8. Resource Usage Monitoring: For large log files or large-scale conversion operations, `relog` can make intensive use of resources such as CPU and memory. Monitor resource usage to ensure your system is not overloaded.
9. Backup: Before making major changes to performance data, create a backup to restore the current state.
10. Use documentation: Consult the `relog` command documentation for the specific options and parameters to ensure you understand and use the functionality correctly.
By keeping these points in mind, you can ensure that the `relog` command is used safely and effectively.
