Rather than have the separate write-chocolateysuccess and write-chocolateyfailure scripts as well as some other functions (such as Chocolatey-Update and Chocolatey-Nuget to name a few) that all provide their own messaging and logging, it would be great to pipe all the info out of those scripts to a centralized logging function. This may make it easier to integrate into Enterprise systems.
For our enterprise implementation, I am creating a Sinatra web service to handle reporting of any Chocolatey activity that changes a system. I am working on funneling all info I need to one function so I may be able to contribute to this project if that is something you might be interested in.
Rather than have the separate write-chocolateysuccess and write-chocolateyfailure scripts as well as some other functions (such as Chocolatey-Update and Chocolatey-Nuget to name a few) that all provide their own messaging and logging, it would be great to pipe all the info out of those scripts to a centralized logging function. This may make it easier to integrate into Enterprise systems.
For our enterprise implementation, I am creating a Sinatra web service to handle reporting of any Chocolatey activity that changes a system. I am working on funneling all info I need to one function so I may be able to contribute to this project if that is something you might be interested in.