2

#PSTip Monitor file growth using WMI

Note: This tip requires PowerShell 2.0 or above.

When running long running scripts, we prefer to log the activities performed to a log file. By the very nature of these tasks, you may find yourself in a situation where you need to truncate the log file and start writing to a new log location or completely stop logging when we find that the log is becoming larger than it should be. This is usually done to preserve the readability of the log files and also, in some cases, to ensure we don’t use up all available disk space.

There is no built-in cmdlet to do this. But, thankfully, WMI provides events we can use to achieve this. Let us see how:

$query = "Select * from __InstanceModificationEvent WITHIN 5 WHERE TargetInstance ISA 'CIM_DataFile' AND TargetInstance.Name='C:\\Logs\\test.log'"

Register-WmiEvent -Query $query -Action {
    Write-Host "Current file size is: " $Event.SourceEventArgs.NewEvent.TargetInstance.FileSize
    $prevSize = $Event.SourceEventArgs.NewEvent.PreviousInstance.FileSize
    $curSize = $Event.SourceEventArgs.NewEvent.TargetInstance.FileSize
    if ($curSize -gt $prevSize) {
        $bytes = $curSize - $prevSize
        Write-Host "File grew by: $bytes bytes"
    } else {
        $bytes = $prevSize - $curSize
        Write-Host "File reduced by: $bytes bytes"
    }
}

In the above snippet, we used CIM_DataFile WMI class to monitor the changes made to a log file at C:\Logs\test.log. The WMI events contain two instances of the WMI class we are looking at. This includes a PreviousInstance and a TargetInstance — which represents the most up-to-date instance. The CIM_DataFile class provides a property called FileSize which can be used to determine (using the Previous and Target instances) whether the file grew in size or reduced.

When this registered WMI event triggers, we can see the changes to the file size at the console.

Although we used a simple Write-Host method to show the file size changes, in a proper implementation we may want to use the decision block to perform something like truncating the existing log file, etc.

Make a note that the event subscriptions made using Register-WMIEvent cmdlet are temporary subscriptions. This means that whatever action we have defined in the script block won’t be executed once the PowerShell host is closed. However, you can use WMI Permanent event consumers to use WMI events irrespective of the PowerShell host state.

Filed in: Columns, Tips and Tricks Tags: , , ,

2 Responses to "#PSTip Monitor file growth using WMI"

Leave a Reply

Submit Comment

© 2016 PowerShell Magazine. All rights reserved. XHTML / CSS Valid.
Proudly designed by Theme Junkie.
%d bloggers like this: