title: Enterprise Library Logging Application Block options
body: <p>Is the logging application block able to handle these situtations or combinations of them?</p>
  
  <ul>
  <li>If logging fails, do not throw an exception
  
  <ul>
  <li>for specific exceptions/exception types only</li>
  </ul></li>
  <li>If logging fails, fallback to another type(ie database logging fails, fall back to emailing or net send)</li>
  </ul>
  
  <p>Example of my actual usage case:</p>
  
  <p>I am writing a ticketing system for our team. If emailing the team on a new ticket creation fails, I want it to report that to the exception/error log, but not bubble that up to the user, regardless of how deep in the fallback stack the logging fails, the user doesn't need an error message, the ticket saved. some error locations/exceptions I would want bubbled up, but most of the ones I'm dealing with right now I do not. </p>