2

How can I enable logging of any exceptions that occur in my handlers, or codecs etc. in IIS?

When googling for that, I found a couple of different ways on how to setup tracing. One of those actually worked, but the trace file (xml) is not very user-friendly. I'd like to have something like a standard text log file that I can view and manipulate using standard tools.

Evgeniy Berezovsky
  • 18,571
  • 13
  • 82
  • 156

1 Answers1

3

OpenRasta uses TraceSources to log requests, so you can use any implementation of log files for tracesources by providing the right configuration in your web.config.

   <system.diagnostics> 
    <sources> 
     <source name="openrasta" switchName="OpenRasta"> 
       <listeners> 
         <add name="ErrorLog" /> 
       </listeners> 
     </source> 
   </sources> 
   <switches> 
     <!--<add name="OpenRasta" value="Warning,Error"/>--> 
     <add name="OpenRasta" value="All"/> 
   </switches> 
   <sharedListeners>

     <add name="ErrorLog" 
          type="System.Diagnostics.TextWriterTraceListener" 
          initializeData="c:\myListener.log" /> 
   </sharedListeners> 
 </system.diagnostics>

I'm not sure however what you mean by standard text log files. Standard log files use standard logs that IIS generates itself already, this part of your logging does not change and is configured the usual way in IIS.

SerialSeb
  • 6,701
  • 24
  • 28
  • Thanks Seb. I know it was an embarrassingly basic question, but thanks to your snippet I figured out what the problem was - the examples that I copy-and-pasted used DefaultTraceListener or XmlWriterTraceListener, with TextWriterTraceListener the output is finally readable! – Evgeniy Berezovsky Oct 17 '11 at 08:59