RFC for pluggable script block/AMSI logging model

from #161/ #106

@PowerShell/powershell-committee discussed this one in detail today. We believe that there's massive value in figuring out how to tee ScriptBlock and AMSI style logs off to remote logging providers, but a bunch of the semantics in this RFC are specific to Splunk.

Instead, we think an RFC should be authored that builds a provider/plugin model for allowing multiple remote logging providers. This RFC should also give consideration to whether local logging targets should be treated the same way (e.g. if you want to exclusively log to a remote target, maybe in serverless/stateless scenarios). There should also be a consideration of whether we should have something like a Get-PSLog or Write-PSLog that are agnostic to logging providers.

The PowerShell Team has a strong interest in picking this up, but we have no idea when we can get to it right now. We only know that it should be a flexible, pluggable model.

Comienza leyendo este RFC junto con los issues #161 y #106, y después revisa la discusión del PowerShell Committee referenciada en el issue. El trabajo propuesto es un RFC para un modelo flexible de provider/plugin para el registro al estilo de ScriptBlock y AMSI, que cubra múltiples providers remotos, destinos locales y comandos independientes del provider, como Get-PSLog o Write-PSLog.