Logging to Multiple Destinations

[KnifMelti]

I have a draft of an extended logging (function Write-ToLog {}):

    param (
        [Parameter(Mandatory = $true)]
        [string]$LogMsg,
        [string]$LogColor = "White",
        [switch]$IsHeader,
        [string]$Component = "WAU",
        [string]$LogLevel = "1",  # 1=Information, 2=Warning, 3=Error
        [string]$LogSource = "WAU",
        [bool]$UseCMLog = $false,
        [bool]$UseEventLog = $true
    )

• Standard log file as it is +
• Configuration Manager log file (if "$env:windir\CCM\CMTrace.exe" OR "${env:ProgramFiles(x86)}\Configuration Manager Support Center\CMLogViewer.exe" exists) +
• Windows Event Log

Live on my home client.

[Romanitho]

If it's necessary, then yes, I agree. Personally, I would focus on simplifying things, and the current logging probably provides sufficient information already. However, I understand the need for this, so please go ahead 😇

[Romanitho]

By the way, when time allows, I'd like to work on a complete overhaul of the project to simplify, harmonize, and streamline the code.

[KnifMelti]

The current log is marveoulus at providing real-time information from WinGet itself, but lacks information those above mentioned readers can use to filter, etc, etc...
Event Log to being able to centralize (Intune client deletes the Symlinks created) logs.

Then I'll now focus on the log rotation and in your coming harmonizing you can replace the log color yellow (=warning in log land) in the outputs 😏

[LucaMoor]

Not directly related to this, but im thinking about adding the functionality to Upload the Logs directly to Log Analytics to analyze them and get notifications about whats happening.

@Romanitho Where would you suggest to store Informations like the Log Analytics Workspace URL (Endpoint) and the Keys / Token etc. ?

[Romanitho]

Probably, like other settings, in the registry, I guess.