Log cleanup automation in PowerShell - Time & Space Complexity

Time Complexity: Log cleanup automation

O(n)

Understanding Time Complexity

When automating log cleanup, it is important to understand how the time to delete files grows as the number of log files increases.

We want to know how the script's work changes when there are more logs to clean.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

# Get all log files older than 7 days
$oldLogs = Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-7) }

# Delete each old log file
foreach ($log in $oldLogs) {
    Remove-Item $log.FullName
}

This script finds all log files older than 7 days and deletes them one by one.

Identify Repeating Operations

• Primary operation: Looping through each old log file to delete it.
• How many times: Once for each log file older than 7 days.

How Execution Grows With Input

As the number of old log files increases, the script deletes more files one by one.

Input Size (n)	Approx. Operations
10	About 10 delete operations
100	About 100 delete operations
1000	About 1000 delete operations

Pattern observation: The work grows directly with the number of files to delete.

Final Time Complexity

Time Complexity: O(n)

This means the time to clean logs grows linearly with the number of old log files.

Common Mistake

[X] Wrong: "Deleting files all at once is instant and does not depend on how many files there are."

[OK] Correct: Each file must be deleted separately, so more files mean more work and more time.

Interview Connect

Understanding how scripts scale with input size helps you write efficient automation and explain your code clearly in interviews.

Self-Check

"What if we used a command that deletes all files in one call instead of looping? How would the time complexity change?"

Practice

1. What is the main purpose of automating log cleanup using PowerShell scripts?

easy

A. To delete old log files and free up disk space

B. To create new log files automatically

C. To rename log files for better organization

D. To compress log files for faster access

Solution

1. Step 1: Understand log cleanup goal

   The goal is to remove old log files that are no longer needed to save disk space.

2. Step 2: Identify automation benefit

   Automating this process ensures logs are cleaned regularly without manual effort.

3. Final Answer:

   To delete old log files and free up disk space -> Option A

4. Quick Check:

   Log cleanup = delete old logs [OK]

Hint: Log cleanup means removing old logs to save space [OK]

Common Mistakes:

• Confusing cleanup with creating or renaming logs
• Thinking cleanup compresses files instead of deleting
• Assuming automation creates logs automatically

2. Which PowerShell command correctly lists log files older than 30 days in the folder C:\Logs?

easy

A. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(30) }

B. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.CreationTime -gt (Get-Date).AddDays(-30) }

C. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-30) }

D. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.CreationTime -lt (Get-Date).AddDays(30) }

Solution

1. Step 1: Identify correct date filter

   We want files older than 30 days, so LastWriteTime should be less than (Get-Date).AddDays(-30).

2. Step 2: Check command syntax

   Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-30) } uses LastWriteTime -lt (less than) 30 days ago, correctly filtering old files.

3. Final Answer:

   Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-30) } -> Option C

4. Quick Check:

   Older than 30 days = LastWriteTime -lt (Get-Date).AddDays(-30) [OK]

Hint: Use -lt (less than) with AddDays(-30) for files older than 30 days [OK]

Common Mistakes:

• Using -gt instead of -lt for older files
• Filtering by CreationTime instead of LastWriteTime
• Using AddDays(30) instead of AddDays(-30)

3. What will be the output of this PowerShell script?

Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-7) } | Remove-Item -WhatIf

medium

A. Throws an error because Remove-Item cannot be piped

B. Lists all .log files older than 7 days and deletes them

C. Deletes all .log files regardless of age

D. Shows which .log files older than 7 days would be deleted without deleting

Solution

1. Step 1: Understand the pipeline

   The script finds .log files older than 7 days using Get-ChildItem and Where-Object.

2. Step 2: Analyze Remove-Item with -WhatIf

   -WhatIf shows what would happen without deleting files, so no files are removed.

3. Final Answer:

   Shows which .log files older than 7 days would be deleted without deleting -> Option D

4. Quick Check:

   -WhatIf shows actions without executing [OK]

Hint: Remove-Item -WhatIf previews deletion without removing files [OK]

Common Mistakes:

• Thinking files are deleted with -WhatIf
• Assuming Remove-Item cannot be piped
• Confusing filter for files newer than 7 days

4. Identify the error in this PowerShell script intended to delete log files older than 15 days:

Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-15) } | Remove-Item

medium

A. The filter uses -gt instead of -lt, so it deletes newer files

B. Remove-Item cannot be used in a pipeline

C. Get-ChildItem does not support -Filter parameter

D. The script is missing the -Recurse flag

Solution

1. Step 1: Check the date comparison operator

   -gt means greater than, so it selects files newer than 15 days, opposite of intended.

2. Step 2: Confirm correct operator for old files

   To delete files older than 15 days, use -lt (less than) with AddDays(-15).

3. Final Answer:

   The filter uses -gt instead of -lt, so it deletes newer files -> Option A

4. Quick Check:

   Older files need -lt, not -gt [OK]

Hint: Use -lt for files older than a date, not -gt [OK]

Common Mistakes:

• Using -gt instead of -lt for filtering old files
• Thinking Remove-Item can't be piped
• Assuming -Filter is unsupported by Get-ChildItem

5. You want to automate deleting log files older than 10 days from C:\Logs and log the deleted filenames to deleted_logs.txt. Which script correctly does this?

hard

A. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-10) } | Remove-Item; Out-File -FilePath 'deleted_logs.txt' -InputObject 'Deleted logs' -Append

B. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-10) } | ForEach-Object { Remove-Item $_.FullName; $_.FullName | Out-File -FilePath 'deleted_logs.txt' -Append }

C. Remove-Item -Path 'C:\Logs\*.log' -Recurse -Force; Get-ChildItem 'deleted_logs.txt' | Out-File -FilePath 'deleted_logs.txt' -Append

D. Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Remove-Item; Add-Content -Path 'deleted_logs.txt' -Value 'Logs deleted'

Solution

1. Step 1: Filter files older than 10 days

   Use Where-Object with LastWriteTime -lt (Get-Date).AddDays(-10) to select old logs.

2. Step 2: Remove files and log names

   ForEach-Object removes each file and appends its name to deleted_logs.txt using Out-File -Append.

3. Final Answer:

   Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-10) } | ForEach-Object { Remove-Item $_.FullName; $_.FullName | Out-File -FilePath 'deleted_logs.txt' -Append } -> Option B

4. Quick Check:

   Filter old files + remove + log names = Get-ChildItem -Path 'C:\Logs' -Filter '*.log' | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-10) } | ForEach-Object { Remove-Item $_.FullName; $_.FullName | Out-File -FilePath 'deleted_logs.txt' -Append } [OK]

Hint: Use ForEach-Object to remove and log each file name [OK]

Common Mistakes:

• Filtering with -gt instead of -lt
• Logging only a fixed string, not filenames
• Deleting files without logging
• Using Remove-Item without filtering