Skip to main content

Removing Identical Content from Multiple Text Logs

This week I am delivering an advanced PowerShell course in Norfolk, VA.  This is my second week with this group of inspiring PowerShell Rock Stars so I decided to push this group a little earlier than usual and I had them help me develop a script to help an individual who posted a question on PowerShell.com (http://powershell.com/cs/forums/t/16403.aspx?PageIndex=1

His task was to examine 3 different text based logs.  Should there be a line that is the same in each of the 3 logs, that line was to be removed from each log.  Sounds simple.  The problem that he was looking at is that his logs were hundreds of thousands of lines long.  This is a perfect example of how to apply PowerShell to a real world situation. We did this as a brain storming session.  For the sake of time, we did not convert this into a cmdlet or a parameterized script.  We have to save some of the fun for the guy we were helping.  Here are our results:

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

# Cast three variables of of type [System.Collections.ArrayList]

# to hold the contents of each log.  Use the Get-Content cmdlet

# to populate the ArrayLists.

 

[System.Collections.ArrayList]$Log1 = Get-Content -Path "Log1.txt"

[System.Collections.ArrayList]$Log2 = Get-Content -Path "Log2.txt"

[System.Collections.ArrayList]$Log3 = Get-Content -Path "Log3.txt"

 

# Create a new ArrayList called $List to hold all strings that

# are present in each event log.

 

$List = New-Object System.Collections.ArrayList

 

# Utilizing Log1 as our control, perform a comparison operation to

# Log2 and Log3.  If they both report $TRUE (A match was found) then

# add that string to $List.

ForEach ($L in $Log1)

{

 

    If (($L -in $Log2) -and ($L -in $Log3))

    {

       $List.Add($L)

    }

 

 

}

 

# Cycle through $List and utilize the "Remove" method

# of the ArrayList to clear that cell of the array out

ForEach ($Item in $List)

{

    $Log1.Remove($Item)

    $Log2.Remove($Item)

    $Log3.Remove($Item)

 

}

 

# Commit the three filtered logs to new files.

$Log1 | Out-File -FilePath "Log1Filtered.txt"

$Log2 | Out-File -FilePath "Log2Filtered.txt"

$Log3 | Out-File -FilePath "Log3Filtered.txt"

In lines 5 – 7, we used an ArrayList.  The advantage of this data type (http://msdn.microsoft.com/en-us/library/system.collections.arraylist(v=vs.110).aspx) is that we have the Remove() method.  When we execute the Remove() method on data in the array, it automatically re-dimensions the array after removing the specified content.

Line 12 creates the ArrayList that will hold the content of any cell from $Log1, $Log2, and $Log3 that is present in all three logs.  We will use this information to remove content from those logs later.

Line 17-26 is where we are searching for content that is present in all three logs.  We are using $Log1  as our control for the ForEach loop. 

Line 20 utilizes 2 comparison operators joined by the –and logical operator.  Each of these comparison operations is using the –in operator.  Traditionally, we would have used a ForEach loop to search each of these other two logs.  In this case, we are using the functionality of the –in comparison operator provided to us by PowerShell.  It will return $True if the other logs contain the string that we are searching for.  If both $Log2 and $Log3 contain the string, then we add that string to $List.

Lines 30-36 cycle utilize the Remove method of the ListArray object to remove each string from all three array.

Lines 39 – 41 write new filtered versions of all three logs that do not  contain strings that are identical

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...