LogMonitor does not capture STDOUT

[clarenceb]

LogMonitor is useful for routing Event Logs, ETW Providers, and Custom App logs to STDOUT for log collection but it doesn't capture STDOUT logs as well. I want to include STDOUT/STDERR logs in addition to the sources supported so that I have better log coverage.

[iankingori]

Hey @clarenceb, kindly share a use case for this feature.

From my understanding container runtimes already read logs from stdout and stderr. LogMonitor reads from the other sources and writes to stdout so we'd need to filter out what LogMonitor has written to avoid getting stuck in a loop.

[clarenceb]

@iankingori I will test this again but last time I was trying to write logs to STDOUT from an asp.net app and the logs were not being collected when I used LogMonitor in the same container. So, I wanted STDOUT/STDERR collection plus what LogMonitor provides. An example would be if I configure something like serilog where some streams go to STDOUT/STDERR and others might go to a file, EventLog, ETW, etc. -- I want all of them to be collected.