title: Play framework stack trace logging and logging configuration
body: <p>With play framework's default logger, I get full exceptions' stack traces in play's application log, and an abbreviated version of the same stack traces in the console. I have three basic questions about the logging:</p>
  
  <ol>
  <li><p>In one case, I feel there may be some information missing. What does something like <code>... 3 common frames omitted</code> actually mean, and can I somehow configure to see those omitted frames?</p></li>
  <li><p>How do I control whether the console shows a full stack trace v.s. a partial one v.s. just some exception title without a stack trace?</p></li>
  <li><p>Can I replace the default logger with any of the following ones, or should I use those ones only for my own logging but keep the framework logging as is? will switching to those loggers break the non-blocking nature of play? <a href="https://github.com/typesafehub/scala-logging" rel="nofollow">scala-logging</a>, <a href="https://github.com/typesafehub/scala-logging" rel="nofollow">log4s</a>, <a href="https://code.google.com/p/zero-log/" rel="nofollow">zero-log</a>.</p></li>
  </ol>
  
  <p>Hopefully, with your answer, I can focus more on my application and less so on logging infrastructure, so thanks in advance!</p>