Massimo Bonvicini
Massimo Bonvicini
Hi @kilale, thank you for your feedback, really appreciated. Personally I don't agree on adding a system call every time you produce a log record and it's not inherent to...
Maybe you need to pass it as variable during Target configuration. Provide me an example, if you can
Take a look at the [ElasticSearch](https://github.com/EsOsO/Logging/blob/master/Logging/targets/ElasticSearch.ps1) target Flatten variable, maybe is what you need. I don't get your needs, sorry. You want to call `Write-Log -Level DEBUG -Message 'Hello, World!'...
Sorry to be late commenting, I'm currently low on time. I'll try to look into this asap, meanwhile feel free to pull a patch
Sorry, I completly missed your messages. Love the implementation, you can merge with upstream. Thank you
You're right. Is due to the target to "present" the log line (think it about MVC). If you have anything working feel free to PR a patch.
The module objects are globally scoped, maybe we can provide a function to clear the targets. You could try removing the module, it should cleanup all the vars used.
Seems fine to me. @tosoikea would you take care of implementing?
Right now we cannot implement strucuterd logging (although I'd like it) cause the form `Write-Log -Message 'Hello, {0}!' -Arguments 'Powershell'` uses powershell string formatting and doesn't work on named parameters...
Please go on, I didn't write anything yet.