Start-Transcript #17588Description
Summary of the new feature / enhancement
Judging from the StackOverflow questions, it appears to me that custom log files implementations are more often used then the native Start-Transcript cmdlet and suspect that this is due to the fact enterprise companies (as the one I am working for) want their own logging facilities which might be a specific log format (e.g. including a specific time stamp per entry) up till writing (specific) entries to a database.
Proposed technical implementation details (optional)
A -Script <ScriptBlock> parameter that refers to a script that is called at each logging event. Within the script (which might need to run in a different scope), I would expect to have access to information (via current item ($_)?) as:
- A reference to thr output streams since last event
- The timestamp of the event (basically the current time)
- Transcript properties/parameters (as the
Pathif supplied) - ...