Currently error logs are written to a file and sent to all people defined in config file via email. I don't think this is a good way to keep track of errors. It is hard to analyze performance using this unorganized format.

One thing we could do is keep information about errors in a separate database. This will allow us to split error reports into a set of attributes and simplify analysis process. Set of attributes might look like this:

• timestamp
• request url
• status code
• revision
• error message