This is the built-in help made by Microsoft for the command 'Export-Counter', in PowerShell version 2 - as retrieved from
Windows version 'Microsoft® Windows Vista™ Ultimate ' PowerShell help files on 2016-06-23.
For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.
The Export-Counter cmdlet takes PerformanceCounterSampleSet objects and exports them as counter log files.
Export-Counter [-Path] <string> -InputObject <PerformanceCounterSampleSet[]> [-Circular <switch>] [-FileFormat <string>] [-Force <switch>] [-MaxS
ize <int>] [<CommonParameters>]
The Export-Counter cmdlet exports performance counter data (PerformanceCounterSampleSet objects) to log files in binary performance log (.blg), c
omma-separated value (.csv), or tab-separated value (.tsv) format. You can use this cmdlet to log or relog performance counter data.
Export-Counter is designed to export data that is returned by the Get-Counter and Import-Counter cmdlets.
Note: Export-Counter runs only on Windows 7, Windows Server 2008 R2, and later versions of Windows.
<
Online version: http://go.microsoft.com/fwlink/?LinkID=138337
Get-Counter
Import-Counter
<
-------------------------- EXAMPLE 1 --------------------------
C:\PS># Export-Counter
Description
-----------
This command exports counter data to a .blg file.
The command uses the Get-Counter cmdlet to collect processor time data. It uses a pipeline operator (|) to send the data to the Export-Counter cm
dlet. The Export-Counter command uses the Path variable to specify the output file.
C:\PS> get-counter "\Processor(*)\% Processor Time" -max 50 | export-counter -path $home\counters.blg
Because the data set might be very large, this command sends the data to Export-Counter through the pipeline. If the data were saved in a variabl
e, the command might use a disproportionate amount of memory.
-------------------------- EXAMPLE 2 --------------------------
C:\PS># Export-Counter
Description
-----------
These commands convert a CSV file to a counter data BLG format.
The first command uses the built-in Windows PowerShell conversion feature to store the value of 1 gigabyte (GB) in bytes in the $1GBinBytes varia
ble. When you type a value followed by K (kilobyte), MB (megabyte), or GB, Windows PowerShell returns the value in bytes.
C:\PS> $1GBinBytes = 1GB
The second command uses the Import-Counter cmdlet to import performance counter data from the Threads.csv file. The example presumes that this fi
le was previously exported by using the Export-Counter cmdlet.
A pipeline operator (|) sends the imported data to the Export-Counter cmdlet. The command uses the Path parameter to specify the location of the
output file. It uses the Circular and MaxSize parameters to direct Export-Counter to create a circular log that wraps at 1 GB.
C:\PS> import-counter threads.csv | export-counter -path threadtest.blg -circular -maxsize $1GBinBytes
-------------------------- EXAMPLE 3 --------------------------
C:\PS># Export-Counter
Description
-----------
This example shows how to get performance counter data from a remote computer and save the data in a file on the remote computer.
The first command uses the Get-Counter cmdlet to collect working set counter data from Server01, a remote computer. The command saves the data in
the $c variable.
C:\PS> $c = get-counter -computername Server01 -counter "\Process(*)\Working Set - Private" -maxSamples 20
The second command uses a pipeline operator (|) to send the data in $c to the Export-Counter cmdlet, which saves it in the Workingset.blg file in
the Perf share on the Server01 computer.
C:\PS> $c | export-counter -path \\Server01\Perf\WorkingSet.blg
-------------------------- EXAMPLE 4 --------------------------
C:\PS># Export-Counter
Description
-----------
This example shows how to use the Import-Counter and Export-Counter cmdlets to relog existing data.
The first command uses the Import-Counter cmdlet to import performance counter data from the DiskSpace.blg log. It saves the data in the $all var
iable. This file contains samples of the "LogicalDisk\% Free Space" counter on more than 200 remote computers in the enterprise.
C:\PS> $all = import-counter DiskSpace.blg
The second command uses the CounterSamples property of the sample set object in $all and the Where-Object cmdlet (alias = "where") to select obje
cts with CookedValues of less than 15 (percent). The command saves the results in the $lowSpace variable.
C:\PS> $lowSpace = $all.countersamples | where {$_.cookedvalues -lt 15}
The third command uses a pipeline operator (|) to send the data in the $lowSpace variable to the Export-Counter cmdlet. The command uses the path
variable to indicate that the selected data should be logged in the LowDiskSpace.blg file.
C:\PS> $lowSpace | export-counter -path LowDiskSpace.blg