title: Analyzing web application usage and user patterns using DB/application server logs?
body: <p>I assume that most of the analyzing and tracking is done based on the data gathered from browser actions like page requests. Tools like AWStats, Google Analytics and Omniture take place in this.</p>
  
  <p>But there is also good amount of data available in databases or service level logs. For example GWT based application might be a bit tricky to analyze. Or in case of a financial application customer might be interested in suspicious transfers.</p>
  
  <p>So, please share your best practices:</p>
  
  <ul>
  <li>What kind of approaches you have implemented for DB or log analysis?</li>
  <li>Do you use some existing tools or your own in-house products?</li>
  <li>Are you happy just to follow which functionality is the used most one and how fast it is processed?</li>
  <li>Or do you actually store user action paths and use those to spot unusual patterns?</li>
  </ul>