Posts RSS Comments RSS 253 Posts and 408 Comments till now

Write-Log… What should it be?

Goal:

Write a Logging Script/Module with functionality similar to Log4Perl : Link to Log4Perl Info

If you have any ideas on what functionality it should have please let me know by leaving a comment.

8 Responses to “Write-Log… What should it be?”

  1. on 26 Feb 2010 at 7:36 amGary

    Why not just wrap Log4Net in a few commandlets? Or, just invoke Log4Net in your script. Works pretty well for us.

  2. on 26 Feb 2010 at 9:09 amChad Miller

    I haven’t check this out, but I saw a note about alternate open source project to Log4Net called NLog http://nlog-project.org/home, might be worth a look.

  3. on 26 Feb 2010 at 12:52 pmVoyager

    Why not use log4net under PowerShell ?

  4. on 26 Feb 2010 at 1:02 pmtshell

    I will definitely take a look at Log4Net… great idea.

  5. on 27 Feb 2010 at 5:18 amVoyager

    See to http://www.codeplex.com/Log4Posh

  6. on 08 Mar 2010 at 12:10 pmJim_B

    Is there some reason the windows event log isn’t good enough? Write-EventLog will write to a classical event log.

  7. on 09 Mar 2010 at 7:35 amtshell

    Event Logs don’t cut it when you have 100s of hosts to parse and the format is well… blah.

  8. on 17 Apr 2010 at 8:56 amDoug

    log4net functionality is almost perfect (being able to log to different sources based on simple xml config file). I’ve had success with it, except for being able to log to a database, there seems to be some sort of bug when using Powershell specifically to log to SQL DB with log4net. I have posted some details to:

    http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.powershell&tid=91ed1088-75b3-4ebc-9585-06e599259a83&cat=en_us_4200CF39-8075-8AEF-F08A-B4D1E076AE83&lang=en&cr=us&sloc=&p=1

Trackback this post | Feed on Comments to this post

Leave a Reply

You must be logged in to post a comment.