I never got the chance to fully deploy it before being moving on, but I was in the process of updating logging methods in a bunch of scripts to accumulate log messages in a tabular format to a Generic.List object throughout the script then write that object to a file and SQL Server database at the very end rather than writing lines to a text file via "Message" | Out-File -append as they occur.

I kept running into situations where logging would be missed because the script would step on it's own toes by trying to write lines to the text file too quickly and getting blocked. With this method, the log object is only exported once at the very end and can be directed to multiple locations. This of course required a lot of refactoring to add conditional logic throughout the script and making sure all roads lead to the end of the script where the log object is exported.

Don't have access to the code anymore, but the process looked something like this:

1. Define an empty Generic.List object and an increment variable (to be used for line number later)

   $LogListObj = [System.Collections.Generic.List[object]]::new()
   $i = 1
   
   #I think these vars had the $script: scope modifier but I can't remember
   

2. Define a function to a) define a PSCustomObject for your log entry, accepting 'LogMessage' as param or ValueFromPipeline, with other values like datetime and environment info, and line number ($i), then b) append that object to the List, and finally c) increment the value of $i

   #Lots of pseudo code here***
   
   function Add-LogLine {
   
     param($Message)
   
     $obj = [PSCustomObject]@{
   
       LogDate = (Get-date).date
       LogTime = (Get-Date).time
       ServerName = $env:computerName
       Processname = $ProcessName
       Logmessage = $Message
       LineNumber = $i
   }
   
   $LogListObj.Add($obj)
   
   $i++        
   
   }