title: Dynamically reconfigure Log4Net
body: <p>I'm looking for tips on the best way to reconfigure the Log4Net logging level dynamically in my ASP.NET apps.  I generally use a simple configuration where the root logger defines the default logging level, e.g.</p>
  
  <pre><code>&lt;log4net&gt;
      &lt;root&gt;
      &lt;level value="INFO" /&gt;
      &lt;appender-ref ref="..." /&gt;
      &lt;appender-ref ref="..." /&gt;
      ... etc ...     
      &lt;/root&gt;
      ... etc
  </code></pre>
  
  <p>and there may be several appenders, each with filters to define the logging levels they use.</p>
  
  <ol>
  <li><p>The first thing I'd like to be able to do would be to allow Administrators to connect to an admin page that enables them to (a) view the current level for the root logger and (b) dynamically change it.  I don't want to use "ConfigureAndWatch" and write to the configuration file on disk because I don't want these changes to persist when the application is recycled.</p></li>
  <li><p>Next I'd like to go further, and on an Admin page be able to display a TreeView with all current Loggers that exist in the application, and their current logging level.  And allow the administrator to be able to change the logging level selectively at any level of the hierarchy.</p></li>
  </ol>
  
  <p>The idea is to to create a generic admin page that I can put into all my apps that allows administrators to selectively enable DEBUG-level logging dynamically for troubleshooting purposes.</p>
  
  <p>I find the Log4Net APIs a bit confusing, can anyone point to samples or show the best way to achieve this.</p>
  
  <p><strong>Update:</strong></p>
  
  <p>Both answers are equally good so I've accepted the first - thanks. To reprise, I can get all current loggers as follows:</p>
  
  <pre><code>foreach (log4net.ILog log in log4net.LogManager.GetCurrentLoggers())
  {
      log4net.Repository.Hierarchy.Logger logger = 
           (log4net.Repository.Hierarchy.Logger)log.Logger;
      Debug.WriteLine(
          String.Format("{0} Parent {1} Level {2} EffectiveLevel {3}&lt;br&gt;",
          logger.Name,
          logger.Parent.Name,
          logger.Level == null ? "&lt;null&gt;" : logger.Level.Name,
          logger.EffectiveLevel
          )
          );
  }
  </code></pre>
  
  <ul>
  <li><p>EffectiveLevel is the effective level - same as Level if the latter is not null, otherwise inherited from the parent.</p></li>
  <li><p>At least one of the loggers returned above will have the root logger as parent, which enables me to get a reference to the root logger.</p></li>
  </ul>
  
  <p>With the above it should be possible to reconstruct the logger hierarchy.</p>
  
  <p><strong>Update 2</strong></p>
  
  <p>Thanks again.  I've implemented an ASP.NET server control that displays the logger hierarchy in a TreeView with checkboxes, and allows the user to dynamically change the logging level at any node in the hierarchy.  Works great and I'll be putting it on Admin page in all my ASP.NET Web and Web Service apps! </p>